Bill,

One more question. I saw the vfp runtime dll's in the SBT folder. The application is SBT Visionpoint (I believe 10.0) running the vpw.exe. Do you know if this program requires the VFP 6 runtime? It appears as if this is the case. If so, does this mean recompiling in Foxpro for DOS 2.6 is valid?


>Bob,
>
>Maybe someone tried to get into the system with VFP? It sure sounds like it. Hopefully there is still the Foxpro 2.6 developers system on there. You should look for a file called foxprox.exe. Once you find it and run it, I would get into the SBT directory and recompile everything in the SBT root folder. (If you aren't familiar with Foxpro Dos, you have to "set default to " to the directory, you cannot CD like in VFP.) There are also programs in sub folders like AR, AP, etc. but I doubt if anyone would have gotten into those with VFP. Just like sysdata was the main table for the system, sysmult.prg is the main procedure file and contains at least 100 procedures and functions that are used all through the system.
>
>Bill
>>Bill,
>>
>>Thanks for that info. One more problem has popped up. When we try to run the SBT application now, we are getting a message that says the "sysmult.fxp was compiled under a different version of foxpro". So right now nobody can get into the app. Have you seen this before? Should I just recompile the program to fix this issue? As always your help is appreciated.
>>
>>Just to let you know, I believe these issues came up because someone was in the process of running month end activites when a user tried to open the app.
>>
>>
>>
>>
>>>Bob,
>>>
>>>You mentioned that you were interested in what this file was used for so I thought I would reply. This is the main file that is used to track all of the info for the system. It stores things like the locations of the program files and all of the data files and indexes. It also tracks the next invoice number, po number, etc. It contains the links between the modules and the general ledger and saves all of settings for the setup. I guess you could say it is pretty important. <g>
>>>
>>>Bill
>>>
>>>>Thanks Bill. Yes, it was a typo on "sysflg". And thanks for your help. My client thanks you, too.
>>>>
>>>>>Bob,
>>>>>
>>>>>Move it somewhere else and then copy to sysdata.dbf type fox2x. You will probably want to delete sysdatx.cdx also and SBT will recreate it when it starts. Note the different spelling of the CDX file. Also, unless someone made them a batch file called sysflg, they would be running "sysflag", not "sysflg"
>>>>>
>>>>>Bill
>>>>>
>>>>>
>>>>>>Is anyone familiar with SBT running on Foxpro for DOS v 2.6? I have a client who is running SBT and has come across a problem. The consultant who implemented SBT is long gone and I just got a call. They have instructions to run a program called 'SYSFLG.PRG' to fix issues when tables get locked. When running this program, when we encounter the 'USE sysdata' line, the program returns an error 'Not a database file'.
>>>>>>
>>>>>>I transferred this table to my machine and I can view and open it in VFP 8.0. Does anybody know how this can be fixed.
>>>>>>
>>>>>>Thanks in advance for any help in this matter.