Client has Multinet version of SBT 6 for 7 years working on a DOS networked system. DOS system died and I was able to recover all files, however client want to run on an XP machine. No longer used in a Networked system but as standalone single user. They only use the MA modules. Is there a way to tell SBT to work as a single. If I try to make any changes system configuration tells me I am in Multi user environment and need to lock the system for changes. There is NO network??
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SBT 6 install on XP 2
- Thread starter BarryPCI
- Start date
Sorry, BarryPCI. Too old of a system for my knowledge.
The problem is in the sysdata.dbf. One of those chracters in a field has to be changed from Y to N , and of course, change the path of the data and programs.
Edgar
Integrated Bar Code Systems, INC.
The problem is in the sysdata.dbf. One of those chracters in a field has to be changed from Y to N , and of course, change the path of the data and programs.
Edgar
Integrated Bar Code Systems, INC.
-
1
- #3
SBT 6 and 7 are FoxPro 2.6 programs or earlier. In general they will not run dependably on an XP. That is particularly true of the Windows versions. Formally suggest upgrading to Cougar Mountain, but you can also upgrade to Vision Point 10.
Bill Couture
SBTBILL.com
Bill Couture
SBTBILL.com
-
1
- #4
shiftysandy
Technical User
Barry,
I tried the same thing for a client of mine who was using VP9 (still essentially a DOS system). It would run in XP in "Accomodation Mode", but that ruled out networking. So, I am TRYING to move them to VP10.
Now, following up on Edgar's post re: the SYSDATA file. I don't have anything older than VP9 manuals, so I looked at the various SYSDATA formats for each of the modules in the Technical Reference manual (no MA in VP9!), and I couldn't find any field that specifically said anything about multi-user vs. single. Of course, that doesn't mean it doesn't exist; the formats for SYSDATA are nearly as detailed as they should be--lots of data in fields that have no definition in the current manual. Of course, those fields could very well be left over from older versions, and simply carried forward in the SYSDATA records.
IIRC, when my client bought their various versions (they have had Versions 6, then 7, then 9), they had to buy the multi-user version; and, when I installed them I seem to remember something that identified the modules they bought as multi-user. But, age has dulled my memory. That's why they call it "Old Timer's" disease, rather than Alzheimer's!
Jim Lamb
I tried the same thing for a client of mine who was using VP9 (still essentially a DOS system). It would run in XP in "Accomodation Mode", but that ruled out networking. So, I am TRYING to move them to VP10.
Now, following up on Edgar's post re: the SYSDATA file. I don't have anything older than VP9 manuals, so I looked at the various SYSDATA formats for each of the modules in the Technical Reference manual (no MA in VP9!), and I couldn't find any field that specifically said anything about multi-user vs. single. Of course, that doesn't mean it doesn't exist; the formats for SYSDATA are nearly as detailed as they should be--lots of data in fields that have no definition in the current manual. Of course, those fields could very well be left over from older versions, and simply carried forward in the SYSDATA records.
IIRC, when my client bought their various versions (they have had Versions 6, then 7, then 9), they had to buy the multi-user version; and, when I installed them I seem to remember something that identified the modules they bought as multi-user. But, age has dulled my memory. That's why they call it "Old Timer's" disease, rather than Alzheimer's!
Jim Lamb
I really don't think it's a multiuser vs single user issue. The code for single user multiuser is in the general proedure file not SYSDATA. To easy to change there. Anyhow I'm prety sure I've seen VP 9 limping along in multi user environments so I don't think that's it. This is really a Fox issue and not an SBT issue.
Bill Couture
SBTBILL.com
Bill Couture
SBTBILL.com
shiftysandy
Technical User
BarryPCI:
I did some more research on your multi-user/network question.
Turns out my comment re: a separate multi-user version is born out by the SBT documentation. This is a quote from the VisionPoint 2000 (SBT Vers. 9) Build 906 Installation Guide:
"When you buy VisionPoint, you can purchase either the source code (unlimited) version or the compiled (single-user) version.
The single-user version files are stored in a format that the computer can process more readily, but that you cannot modify. SBT supplies a run-time version of FoxPro that you can use to run compiled VisionPoint programs and perform certain database management tasks. Compiled program file names have an ".FXP" extension.
The unlimited version includes the compiled programs and source code, which you can modify using a developer's version of FoxPro. Source code program file names have a ".PRG" extension."
Further, it says: "When you install either version, the .FXP coompiled files are copied to your hard disk. If you have purchased the unlimited version, the installation routine gives you the option to install the .PRG files as well, in case you wish to modify the software."
That also echos my experience installing the system. Since my client DOES run multi-user, and they DO have many modifications to their system, they have the source code (unlimited) version.
So, you most likely have that version. Look in your \SBT folders to see if you have the .PRG files.
Now, more info, again following up on what fitedgar said. I looked through the source code to try and find a field in SYSDATA.DBF that identified single vs. multi-user. The Technical Reference manual alluded to the SYSDATA.DBF "MM" record as containing important information about your installation. However, there is no field DEFINED in that manual that says anything about single or multi-users.
Then, I scanned the source programs. I only found that the programs tested a variable called m0single: .t. equals single user, while .f. equals multi-user. I could NOT find where that variable is set. I used the old Windows 98 "Search" tool (for matching text in .PRG files); and, I used a text search program called "Locate" that came with our SBT source. I searched for "multi" and "m0single", looking at the source of every program that contained that text. Couldn't find any place where m0single is set--only tested.
If you have source, you might try modifying VP.PRG to set m0single to .t. just before calling the next program. Don't know if that will work, but it's worth a try.
Good luck,
Jim
I did some more research on your multi-user/network question.
Turns out my comment re: a separate multi-user version is born out by the SBT documentation. This is a quote from the VisionPoint 2000 (SBT Vers. 9) Build 906 Installation Guide:
"When you buy VisionPoint, you can purchase either the source code (unlimited) version or the compiled (single-user) version.
The single-user version files are stored in a format that the computer can process more readily, but that you cannot modify. SBT supplies a run-time version of FoxPro that you can use to run compiled VisionPoint programs and perform certain database management tasks. Compiled program file names have an ".FXP" extension.
The unlimited version includes the compiled programs and source code, which you can modify using a developer's version of FoxPro. Source code program file names have a ".PRG" extension."
Further, it says: "When you install either version, the .FXP coompiled files are copied to your hard disk. If you have purchased the unlimited version, the installation routine gives you the option to install the .PRG files as well, in case you wish to modify the software."
That also echos my experience installing the system. Since my client DOES run multi-user, and they DO have many modifications to their system, they have the source code (unlimited) version.
So, you most likely have that version. Look in your \SBT folders to see if you have the .PRG files.
Now, more info, again following up on what fitedgar said. I looked through the source code to try and find a field in SYSDATA.DBF that identified single vs. multi-user. The Technical Reference manual alluded to the SYSDATA.DBF "MM" record as containing important information about your installation. However, there is no field DEFINED in that manual that says anything about single or multi-users.
Then, I scanned the source programs. I only found that the programs tested a variable called m0single: .t. equals single user, while .f. equals multi-user. I could NOT find where that variable is set. I used the old Windows 98 "Search" tool (for matching text in .PRG files); and, I used a text search program called "Locate" that came with our SBT source. I searched for "multi" and "m0single", looking at the source of every program that contained that text. Couldn't find any place where m0single is set--only tested.
If you have source, you might try modifying VP.PRG to set m0single to .t. just before calling the next program. Don't know if that will work, but it's worth a try.
Good luck,
Jim
VP program will not do it. Also I think it is already obsolete in that version. You need to look int SBTPROC or SYSPROC, or possibly it is hidden in the .FLL. SBT got rather proprietary about this variable for obvious reasons.
Also the multiuser version works fine on a single work station. It doesn't require a network. Most likely you have path issues in SYSDATA. Even the single user version can access data over the network.
Visual FoxPro is always multiuser so SBT sets exclusive on and counts users in the single user version, which has exactly the same code as the multiuser version. It is really a mater of buying the program with or without source not single or multiuser.
Bill Couture
Also the multiuser version works fine on a single work station. It doesn't require a network. Most likely you have path issues in SYSDATA. Even the single user version can access data over the network.
Visual FoxPro is always multiuser so SBT sets exclusive on and counts users in the single user version, which has exactly the same code as the multiuser version. It is really a mater of buying the program with or without source not single or multiuser.
Bill Couture
- Thread starter
- #8
Well I had a little more time to trouble shoot on my own. The version my client is running is 6.3# of the FoxBase+ runtime library. Since all he wants to do is run the MA Module I was able to have him drop to the "DOT" command and change the m0Single to .t. which solves the running under XP in a Command window. I set up a shortcut that launches SBT with "C:\SBT\MFOXPRUN.EXE MA".
My next task is to get the system to print reports using the NET commands and setting a Generic Printer? Any suggestions?
My next task is to get the system to print reports using the NET commands and setting a Generic Printer? Any suggestions?
- Status
Similar threads
- Locked
- Question