puzzling issue
Posted: Tue Apr 08, 2014 6:20 am
I have a stand alone EXE that updates a PRODUCTS.DBF file with changes from the main store. The changes file is a DBF file that can be gotten either manually or from an FTP site. Once the file is at the remote store, it searches for the products, if found, replaces the data (with any changes), if not found it adds the product.
Once the changes file is retrieved locally, there is no difference in the code that runs.
When I manually bring in the changes file, all is well. If I FTP the file, when done (and the EXE closes) the PRODUCTS.DBf file remains locked and the main program can't access it. We have to reboot the server to free it up. This makes no sense to me as it isn't even the PRODUCTS.DBF file that is FTP'd. The file isn't even opened until the changes file is obtained locally (either manually or via ftp).
after all the changes to the products file have been made, I have a dbcloseall(), then I display the products that have been changed... and that display is working so the dbcloseall() should have closed the file. Additionally, when the EXE terminates (with a QUIT statement) anything open should close.
Any thoughts?
Once the changes file is retrieved locally, there is no difference in the code that runs.
When I manually bring in the changes file, all is well. If I FTP the file, when done (and the EXE closes) the PRODUCTS.DBf file remains locked and the main program can't access it. We have to reboot the server to free it up. This makes no sense to me as it isn't even the PRODUCTS.DBF file that is FTP'd. The file isn't even opened until the changes file is obtained locally (either manually or via ftp).
after all the changes to the products file have been made, I have a dbcloseall(), then I display the products that have been changed... and that display is working so the dbcloseall() should have closed the file. Additionally, when the EXE terminates (with a QUIT statement) anything open should close.
Any thoughts?