Recent content by lachlanK

Yes that is the relevant section. Look in VFP help on the PROGRAM() function, this will give you some insight into how the code snippet works. In addition to the section of code you have cut out, you will need the part which opens the error file: STORE errfile + '.err' TO prgdump...

Have done that now, seems to have corrected problem. Seems strange that (whatever version was on there) could malfunction so badly, I had values mysteriously changing by 1 cent, etc. Cheers, - Lachlan

If you are using macro substitution when building up the query string then this will be the problem. e.g.: myVar = replicate("abc",9999) INSERT .... VALUES ('&myVar', ....) This can produce intermittent errors when the length of the macroed string causes the entire length of the line...

Hi, I have a client / server app using VFP 6.0 + SQL Server 2000 which works successfully over a WAN. Clients have various versions of windows. In the weekend I added another branch to the user base. The 95 / 98 1st edition machines are giving me an "update conflict" error during...

Thank You! Your error handling routine looks very familiar, I guess all VFP programmers go down similar roads in this respect. The vital piece of information I was missing was the existence of the PROGRAM() function. Shame can't get a line number for each... Cheers, - Lachlan

Thanks, but that article didn't really address my query... Anyone else? - Lachlan

Hi, occasionally when VFP crashes, you receive a call stack trace, with line numbers (similar to what you can view from the debugger). Being able to access this from an error handling routine would be extremely useful in trying to track bugs, as often a program will crash in a common function...