General information
Title:
Best way to handle this - SQL writing to VFP?
We have a fox 2.x table that has an inventory quantity ("qty") field. The qty is now going to be in SQL-Server. We need to keep the fox table up-to-date with the real-time qty since some legacy apps still look there for the qty.
I'm thinking of using OLEdb to have SQL-Server write the changes directly to the fox table. I can't load the $@#%# driver so I can't play with it yet.
I can't simply write the changes to VFP after the SQL transaction is committed since there may be a connectivity issue or the VFP record might be locked.
We can use an air-tight data synchronization process that we've used to bring data from remote warehouses to our central processing location every 30 seconds for 2 years now. It's really awesome and quite reliable but we want to do less synchronizing not more.
Aside from the actual quantity number we'll have each of the transactions that caused the inventory to change. This could be part of a solution.
Summary: How can we, with 100% reliability, write data to VFP from SQL? What methods are used? What safeguards?
Thanks,
Mark
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only