|
Post by damien on Jun 12, 2019 1:56:54 GMT 1
Hi Guys, The old DOS CRM program I am using runs nicely in vDos on Win10 and can actually print from other areas of the program fine, eg. picking slip and debtor reports etc But when I try to reprint an invoice I get a Parsing Error, see attached screenshot. Do you think this is likely to be a Printer setup issue or simply an issue with the DOS application itself. We still have this same DOS program running on an old Win7 machine in compatibility mode and it does not have any issues printing an invoice, so I'm a little confused. Much appreciated, Damien
|
|
|
Post by Jos on Jun 12, 2019 7:38:43 GMT 1
Somehow your program doesn’t match the variable FULL_NAME (used in the layout of the invoice?) to actual data. Could you start vDos with the log option (“…vDos.exe” /log), enforce the Parsing Error, and post the generated vDos.log file.
Jos
|
|
|
Post by damien on Jun 12, 2019 23:41:57 GMT 1
Thanks so much for your reply Jos. Please forgive my ignorance, how do I run vDos with the log option. Shortcut properties screenshot attached. Much appreciated, Damien
|
|
|
Post by Jos on Jun 12, 2019 23:53:00 GMT 1
In this situation, just append /log to the target (C:\vDos\vDos.exe).
Jos
|
|
|
Post by damien on Jun 13, 2019 1:03:48 GMT 1
Thank you Jos! Log file attached..... vDos.log (48.82 KB) Many thanks, Damien
|
|
|
Post by Jos on Jun 13, 2019 8:03:49 GMT 1
The only thing that stands out is the failed open attempts of several files: SYSTEM.NSX, MULTI.NSX, PRINTER.NSX, STKCHG.NSX, LABELS.NSX, USERS.NSX
Although seemingly legit files, those are not found/present in the C:\VDOS\DCS directory. Check if the files are misplaces or not copied over from the old system.
If that doesn’t bring anything, I would need a test environment (e.g. the DCS directory) and instructions how to replicate the error. You can remove as much of the data, so the error is still produced.
Jos
|
|
|
Post by damien on Jun 17, 2019 6:46:01 GMT 1
Hi Jos,
This is interesting. The copy we are running on the old machine is now exhibiting the same problem. Have even tried it on DosBox and get still the same error.
Solved: Turns out that the user have never tried to reprint and invoice from before July 2000, the month that GST (Goods and Services Tax) was introduced in Australia. Any invoice before that date causes the parsing error. Any invoice after that date prints fine.
Obviously they modified the application for the new GST system and older pre-GST invoices are not compatible with the new print formatting.
Thanks for you assistance Jos, at least we now have a reason why.
Much appreciated, Damien
|
|