Please Dave if you don’t mind, I guess that was followed by code changes once the .dbf was dropped to update SQL direct?
Regards
Chris.
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Dave Crozier Sent: 18 December 2024 11:58 To: profoxtech@leafe.com Subject: Re: Database Migration Pointers
When I had to upsize to M$ SQL I developed a set of triggers that actioned the SQL updates as they occurred in the Fox DB files. This meant that I was running with two sets of data for ease of use and I gradually dropped the .dbf files once the data in SQL DB was confirmed to be correct. It worked well with little if no speed penalty. I can dig out the trigger procedures if you want. Dave
On Mon, 2 Dec 2024, 13:10 Eric Selje, Eric@saltydogllc.com wrote:
There's a Hentzenwerke book about upsizing your apps to MySQL. It covers a lot of the little gotchas. If you poke around I bet there's a copy floating around somewhere.
Eric
On Fri, Nov 29, 2024 at 3:52 PM MB Software Solutions, LLC < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
Besides what the others said in code and uncoded messages (lol), I recall having to have the remote views database locally (instead of a common location on the network) due to VFP locking something which would cause issues.
Good luck! --Michael
On 11/24/2024 9:42 AM, Chris Davis 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]
_______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/CA+=YCLW3JGnrSXOPfNT7=u+dAtWrvBg9aoM3_590yS... ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.