FoxPro 2.6 Fundamental Question

[FoxProResearch]

Hi Everyone,

Keep in mind that this question is coming from an experienced programmer that has no understanding of the FoxPro 2.6 platform or it's architecture.

I'm investigating methods to integrate with a FoxPro 2.6 system. The system consists of ~60 identical FoxPro databases deployed around the country running a custom order entry system. I need all of these Order Entry systems to communicate the status of their orders every time the status changes. We'll be communicating to some sort of centralized system, what we choose to implement depends on what is possible.

What's the best way for me to accomplish something like this? I'm specifically asking about how FoxPro can communicate with other systems. Figuring out when an order changes is not an issue, but figuring out how to tell another system that the order has changed is what I'm worried about.

For example,
- Can FoxPro insert and update records in a SQL Server database via an ODBC connection?
- Can FoxPro initiate some sort of message to a server that is listening for messages (DDE, COM, HTTP, etc)

Are there other ways of accomplishing this with FoxPro?

A solution to this problem was already attempted but it failed. A service was written that accesses each of the 60 FoxPro systems one at a time and polls the Order Status Data. The problem with this system was that it needed exclusive access to the FoxPro system that it is polling. Because the systems are being used on site, if another user was entering or updating an order, the service would skip that location.

We are looking to replace this system with a more robust solution.

Thanks

 

[TamarGranor]

Yes, FoxPro can talk to SQL Server. In FoxPro 2.6 (which shipped in 1991), you're limited to ODBC. If you go to Visual FoxPro, you can use OLE DB, as well.

FoxPro 2.6 can do DDE. Visual FoxPro can also do OLE.

Tamar

 

[CouponPages]

For clarification, FoxPro 2.6 for DOS can't communicate with anything directly. It lacks any support for OLE, ODBC or DDE.

FoxPro 2.6 for Windows does add some OLE access... but it's not well suited for any serious SQL connectivity. If the application you are working with needs that connectivity and it's too complex to convert to Visual FoxPro, then I would just continue the efforts you already took... with one exception, finding non-exclusive methods to poll the data.

In my experience, other than modifying structures or primary indexes, there are very few times I ever need exclusive use of any database. If the polling program needs to modify large groups of records with a "Replace all... FOR", which can lock the entire table, try changing it to a SCAN... FOR with a replace line. The result is the same, and it will only lock one record at a time. You can place a conditional record lock test in the scan so it can wait for an unlock if it finds an individual lock already in place from another user.