Bad file name or number in module POS3

[tomrubyc]

I am running POS7.1c. When closing out the register and using the Print/Erase/Exit option I get:
"Bad file name or number in line 7 of module POS3 at address 2C7F:4705."
All other POS functions seem normal. Anyone got an idea re how I got here and how I can get around this? Thanks.

[brucef2112]

Your 7.1c problem may be fixed with an upgrade to the current 7.1f. First, try to create a test copy of your register to another folder. Then upgrade it to the latest version and see if that fixes your Close Register problem. If is does, let us know so Dale and his Development Team can do a 'victory jig' and go back to doing nothing.

If not. Answers to the following questions will be very helpful to Dale and the Development Team to help you fix your problem.

What OS are you running?
     DOS, Windows (version?) (running full screen or windowed?), Mac, Some form of Unix, Linx or other with DosBox software or other emulator.

What are some of your main POS configuration settings? (Changing/setting some of these may help answer or fix the problem.) Many of these come into play when the register is closed.
     Using the stock table? if so, what setting you are using.
     Using Sales Recording-Voids?
     Using a printer/no printer? Parallel/USB (are you using Aprint)? If using a printer, does turning the printer 'ON' help?
     Using Auto Reports feature?
     Using the Time Sales or Ticket Sales feature?
     What is your Rounding (of money amounts) set to?
     Are you using the Journal feature? If so, what are its settings?
     Are you using the Network feature? If so does this only happen on the main register? slave register? Both?
     Are you using the Gift Card feature?

Does this happen if you close the register without ringing any sales? After a few sales? after 100 sales? With Return Sales? Voided Sales?

Is your 7.1c from a fresh install or was it upgraded from a previous version?Or several upgrades?

If you leave the computer turned 'OFF' does the problem go away??

Let us know....

[daleadmin]

This seems to have been fixed. tomrubyc was in chat and it turns out that when he attached a printer to his computer (DHPOS was configured to print) that the problem just went away.

Dale

[brucef2112]

Dale does a 'victory jig'.....