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!
Windows 2000 Printing Issues VPW 2000 9.0a 2
- Thread starter tcitjh
- Start date
Hi,
I came across your message and I am having the same problem as you mentioned above. I was wondering if you ever got a fix for the FOXPROW caused a General Protection Fault in module
FOXW2600.ESL at 0001:222D
If so, can you let me know what you did.
Thanks,
Todd
I came across your message and I am having the same problem as you mentioned above. I was wondering if you ever got a fix for the FOXPROW caused a General Protection Fault in module
FOXW2600.ESL at 0001:222D
If so, can you let me know what you did.
Thanks,
Todd
-
2
- Thread starter
- #3
Tood:
We never found a fix.
However, from other testing, we belive that there is an inherrent memory management issue in FP 2.6a.
We have been able to create a strange set of problems on W98SE that only occur when we run FP applications.
Microsoft flatly refuses to even look at the issue. So - we do not ever antiicpate getting a soltuion.
Unfortunately, this leaves us with a major accouting applciation that cannot run on W2K and probably will not run under XP.
If you come up with any information, I would appreciate your sharing it with me.
Good Luck,
Tom
We never found a fix.
However, from other testing, we belive that there is an inherrent memory management issue in FP 2.6a.
We have been able to create a strange set of problems on W98SE that only occur when we run FP applications.
Microsoft flatly refuses to even look at the issue. So - we do not ever antiicpate getting a soltuion.
Unfortunately, this leaves us with a major accouting applciation that cannot run on W2K and probably will not run under XP.
If you come up with any information, I would appreciate your sharing it with me.
Good Luck,
Tom
Guest_imported
New member
- Jan 1, 1970
- 0
Same problems here. I spent hours and finally found a german guy (had to use google translate) to find out what he was talking about. Apparently one can change some code (see below) but i have no sources for my SBT visionpoint so i can't change it and recompile. Has anyone heard of a patch for the runtime instead?
Tom Gusten
Tom Gusten
- Thread starter
- #5
Guest_imported
New member
- Jan 1, 1970
- 0
Looking for a fiz Foxprow General Protection Fault 0001:222d, can anyone help
Jorge
Jorge
RichardatPCDIS
IS-IT--Management
Folks,
I am having trouble with a client that has VP 2000 version 9 build 905.
Their Win98 workstations simply map an F: drive on their netware server to F:\app\vp2000 and they run a shortcut to VPW.exe.
The problem I am having is a new Win98 workstation (yes - this is the last W98 box you can by new - from Micron) doesn't show that "Purchase Orders" is available. When I re-run installation, it says that all purchased modules are installed. From other PCs on the network, I can get to PO. If I go into system manager, I can (on the other workstations) see that PO is installed. On this new workstation, even in SM, it does not show PO. Any suggestions would be GREATLY appreciated. Thank you in advance! I can probably even send you a TGIF gift certificate. Please write soon. Thanks
Richard
I am having trouble with a client that has VP 2000 version 9 build 905.
Their Win98 workstations simply map an F: drive on their netware server to F:\app\vp2000 and they run a shortcut to VPW.exe.
The problem I am having is a new Win98 workstation (yes - this is the last W98 box you can by new - from Micron) doesn't show that "Purchase Orders" is available. When I re-run installation, it says that all purchased modules are installed. From other PCs on the network, I can get to PO. If I go into system manager, I can (on the other workstations) see that PO is installed. On this new workstation, even in SM, it does not show PO. Any suggestions would be GREATLY appreciated. Thank you in advance! I can probably even send you a TGIF gift certificate. Please write soon. Thanks
Richard
You sound like a guy that was mentioned to me from consultant back east. The issues may deal with mem files. Considering that I may have a bid in on this maybe shouldn't be so free with info, but when installing SBT it is usually a good idea to back up the Mem files and then delete them. They contain path info. Sysdata is no longer the only location of file paths so there may be something there too.
Bill Couture
SBTBILL.COM
Bill Couture
SBTBILL.COM
Having the same LaserForms problem with VisionPoint 9.0a.
Also I don't have the source, so I need either the patched compiled version, or source code and fix.
Someone mentioned that a printer driver change may fix the problem....any details ?
thanx all
Also I don't have the source, so I need either the patched compiled version, or source code and fix.
Someone mentioned that a printer driver change may fix the problem....any details ?
thanx all
quicklycomp
Technical User
Hey, I have just started to deal with FoxPro, a company that recently hired me has it, and therefore they'd like me to come up with a fix. Does anybody have a patch or the code to fix the laser forms from 2000 problem? I would really like to get our 98 machines up to 2000 and XP, so any help you could give me would be very much appreciated.
Thanks,
M@
Matt
Thanks,
M@
Matt
Better late then never - except in this case. I too am experiencing problems with SBT VisionPoint Laser Printouts on workstations using Win2k OS. Whenever you try to print Laser forms (which I believe is a DOS app) I get the Foxprow caused a General Protection Fault in module Foxprow.exe.
Did anyone ever get around this problem?
Thanks
Did anyone ever get around this problem?
Thanks
Have been running VisionPoint 2000 on NT;2000;XP and using "Print to file" then print with Notepad.
After talking with Microsoft and SBT several times I do not expect there to be a fix, only workarounds.
Anybody have a better workaround to share?
After talking with Microsoft and SBT several times I do not expect there to be a fix, only workarounds.
Anybody have a better workaround to share?
Mcsew,
I ended up not using the Laser Forms print option and simply changed the Report for PO's SO's and Invoices. Some minor mods to the programs that call the reports to add addional forms like packing slips. The report writer in Foxpro is a little cumbersome - but it can be done. Let me know if you are inclined to go this route and I can tell you the report file names and programs that need modification and even send what I have done if it helps.
I ended up not using the Laser Forms print option and simply changed the Report for PO's SO's and Invoices. Some minor mods to the programs that call the reports to add addional forms like packing slips. The report writer in Foxpro is a little cumbersome - but it can be done. Let me know if you are inclined to go this route and I can tell you the report file names and programs that need modification and even send what I have done if it helps.
We are currently running VP2000 Version 9 build 902 with FP 2.6 on a Win2000 Server. It runs fine, but we have the printing issues as discussed in this forum. While going through some old CDs we discovered a build 905 CD.
I made a copy of the old directory and upgraded SBT. Build 905 works fine when executed locally on the server, but when we try to access SBT from a client (NT), we receive an error that we are missing a SYSMULT.PRG file and to "copy the file to the Program Drive/Directory."
Can anyone assist me offline?
Thank you.
I made a copy of the old directory and upgraded SBT. Build 905 works fine when executed locally on the server, but when we try to access SBT from a client (NT), we receive an error that we are missing a SYSMULT.PRG file and to "copy the file to the Program Drive/Directory."
Can anyone assist me offline?
Thank you.
I'm now able to print from my XP and NT clients, but I can only print reports and not forms. If I try to print using laser forms I receive an error.
Also, If I try to print from a Win9x client, it no longer prints (forms or reports). We get a missing file error. With build 902, the Win9x clients work fine; with build 905 the Win9x clients don't print.
We have FoxPro 2.6 & build 905 for SBT.
Would a later version of FoxPro help? If yes, then what version of FP works well with SBT build 905?
Any ideas?
Also, If I try to print from a Win9x client, it no longer prints (forms or reports). We get a missing file error. With build 902, the Win9x clients work fine; with build 905 the Win9x clients don't print.
We have FoxPro 2.6 & build 905 for SBT.
Would a later version of FoxPro help? If yes, then what version of FP works well with SBT build 905?
Any ideas?
Reading about the problems with SBT 9 and earlier with current editions of Windows is always a bit frustrating. The problem is Foxpro 2.6 which was used by SBT which has since been bought out by ACCPAC. Vision Point 10 is written in VFP 6 and runs well in VFP 7. Vision Point 9 will also run in VFP 6, however it was not formated for it and so the screens look awful.
The solution to the problem is to upgrade to Vision Point 10 which costs about $400 per module and includes source code. I have yet to have a customer have a problem with this.
I have had several customers attempt to load Fox 2.6 patches for running on XP. None has worked well enough for me to recomend. Normally, the printer problems persisted and lockups continued. Going to VP 10 eliminates all of these. I regularly modify Vision Point on an XP, with 10, no problems. With previous issues will not even try it anymore.
I'll probably get flamed for comercialism but the point is there is a solution and it is not overly expensive.
As a point of information when ACCPAC bought SBT many of the SBT dealers left for other products. ACCPAC decided to push the PRO verison. This is a much more powerful package and also much more expensive. ACCPAC dealers who added the SBT or ACCPAC source line generally do not understand Vision Point as no training is provided and the ACCPAC company line is to upgrade to PRO. This is sometimes a very good idea.
However, there are still hundreds if not thousands of "SBT" dealers, certified consultants, and programmers out there. Vision Point is still being used in numerious projects and is alive and well. In fact I am in the process of developing a version on XP that will allow multiple screens to be open at the same time.
Hope this answers everyones questions about these problems and the future of Vision Point or SBT 9.
Bill Couture
The solution to the problem is to upgrade to Vision Point 10 which costs about $400 per module and includes source code. I have yet to have a customer have a problem with this.
I have had several customers attempt to load Fox 2.6 patches for running on XP. None has worked well enough for me to recomend. Normally, the printer problems persisted and lockups continued. Going to VP 10 eliminates all of these. I regularly modify Vision Point on an XP, with 10, no problems. With previous issues will not even try it anymore.
I'll probably get flamed for comercialism but the point is there is a solution and it is not overly expensive.
As a point of information when ACCPAC bought SBT many of the SBT dealers left for other products. ACCPAC decided to push the PRO verison. This is a much more powerful package and also much more expensive. ACCPAC dealers who added the SBT or ACCPAC source line generally do not understand Vision Point as no training is provided and the ACCPAC company line is to upgrade to PRO. This is sometimes a very good idea.
However, there are still hundreds if not thousands of "SBT" dealers, certified consultants, and programmers out there. Vision Point is still being used in numerious projects and is alive and well. In fact I am in the process of developing a version on XP that will allow multiple screens to be open at the same time.
Hope this answers everyones questions about these problems and the future of Vision Point or SBT 9.
Bill Couture
We currently use SBT 3.x\foxpro 2.6 and had a similar issue printing from point of sale to a local recipt printer. We solved the problem by sharing the printer and then editing the arregs98.dbf file to reflect the UNC name of the printer as opposed to LPT1.
Hope this helps.
Hope this helps.
- Status
Similar threads
- Locked
- Question