No, that's pretty much it. I think the only issue I had is if you're using incrementing keys in vfp. IIRC, you need to remove that field from the view, and add it to the backend instead, then don't reference it. I seem to recall some issues with maybe Memo General and/or Blob? Basically few problems and what there were were obvious (crash) and easily fixed. Good luck!
On Sunday, November 24th, 2024 at 9:42 AM, Chris Davis chrisd@actongate.co.uk wrote:
Hi All
Before we start this just figured it would make sense to reach out to you guys for any general advice or pointers you can give.
We have a typical multiuser VFP application using a DBC with DBF’s and local views.
The forms that interact with this data all have a DE and for the deployed versions we have DPATHMGR sorting the DE paths out making everything work.
We have no immediate need to change anything about from front end , it’s relatively straight forward and most of the code is based around TABLEUPDATE and TABLEREVERT.
Our mission is just to loose the DBFs and move the data to SQL as our first pass. No intentions to make use of SQL things like stored procedures , we just want to treat it as a data dump for the moment.
So after using VFPX/UpsizingWizard our initial thoughts are to replace the local view with remote views and then continue with the current method of CRUD via the views.
Anything you feel is worth a heads up on for us to consider before we get on with it?
Regards
Chris
[excessive quoting removed by server]