Vision Point 10 and Visual FoxPro 6.0 Users?

[shiftysandy]

Anyone out there using Vision Point 10 in Windows XP, along with Visual FoxPro 6.0 (actually, any version of VFP)? My client has source, and I'm doing extensive revisions to non-Laser printing output, bypassing the Report Generator code and the .FRM/.FRX files, and getting FoxPro "C0000005" error. Research that on Google, found only one guy who seemed to really know anything about it, and he suggested downloading the latest Service Pack (SP5) which I did. Still, no joy.

Wondering if anyone else is doing something similar.

Many thanks for your input

 

[fitedgar]

If it works in the program, it must be your code.

What module ?

Why are bypassing ?

It is better to have ACCPAC PRO do all the work, capture the output data, manipulate and display it using the Fox Pro Visual report writer. Visual Fox pro is very powerful. I have yet to encounter a problem not able to resolve in Visual Fox Pro.

Edgar
Integrated Bar Code Systems

 

[shiftysandy]

Thanks, Edgar, for responding.

The module is AR, specifically the programs ARPSTM and ARSTMF. I am having to bypass all the REPORT code. My client has a highly modified invoice, with subtotals of the invoice detail, followed by two different types of SHIP classes of items, with subtotals of each, and finally a grand total of the entire invoice. The REPORT command would work fine for the detail items within the main body of the invoice, but the complicated SHIPping items, with their subtotals, just don't lend themselves well to the Report Generator.

Also, for some reason, my modified code--copied from the Vision Point 9 system--fails to get a final total for the invoice. Same code, same processing, but no grand total.

Then, if I run ARPSTM with the modified code, it goes straight through, prints nothing, and gets the "C0000005" error. If I build in breakpoints in ARPSTM, the printing works exactly as it should, except for the final total, but I still get the FoxPro error.

Now, here's something interesting. I can take the Vision Point 9 programs, recompile them in VFP 6.0, and they work like a champ--EXACTLY as they do in VP 6 with the old DOS-based FoxPro 2.6.

I did have an inspiration I'm going to try tomorrow. Obviously, when I modified ARPSTM and ARSTMF, I recompiled them with the SP5 upgraded VFP 6.0. BUT, I didn't recompile the other programs leading up to that (which, by the way, are all identified in the C0000005 error output): VPW, VP, SYSMULT, ARAPP, and ARMENU. Think I'll recompile all those with SP5 and try it then.

Best regards,

Jim Lamb

 

[SBTBILL]

Vision Point 10 is originally compiled in VFP 6. VP 9 was still in FoxPro 2.6 Vision Point 10 works on an XP. Have had lots of customers using it as such.

Bill Couture
SBTBILL.COM

 

[shiftysandy]

SBTBILL,

Thanks for your post. I understand re: VFP 6.0, VP 10, and XP. XP, and more modern hardware, were the primary reasons my client had to consider the move to VP 10.

Don't think I mentioned in my reply to Edgar, but I Google'd for FoxPro error "C0000005" and found very little help, EXCEPT for one fellow from Europe that suggested that one might be able to get rid of that by loading the latest Service Pack--SP5 right now--and installing and recompiling with the updated VFP 6.0/SP5.

Did that, but no joy still.

What really puzzles me is that I can run the modified program without any sort of breakpoints, and it runs straight through, prints NOTHING, and dies with the C0000005 error code. However, when I insert breakpoints throughout the code (WAIT <text> WINDOW statements), the program prints everything exactly as it should EXCEPT the final total. Even prints comments and the footer of the invoice, which occur AFTER the final total--but still terminates with the C0000005 error, though.

Might mention I am using the "@line, position SAY <whatever>" statement to print. As mentioned, it works for everything except the final total.

Mystery!

Many thanks, again, for your post.

Jim Lamb

 

[SBTBILL]

All printing in VFP 6+ should be done through a report form.

However, it may have do do with row position. try reducing the number of rows per page. Column position could be involved, too.

Bill Couture
sbtbill.com

 

[shiftysandy]

I use the same format--different line numbers, but same print position--to print other sub-totals, which print correctly. And, the total fails to print, whether there is only 1 item in the invoice or a page full.