On a RDP shared MS Access database, a great working program sudenly glitched in a module that creates a text file. The backend of this split database was not too big, but the shared frontend had grown 10 over 169megs. The file was not getting created completly with some missing datum. When users started to go to lunch, the file then was created correctly. Repaired and compacted the databasewhich reduced the file size to 21k. The server may have run out of memory. May consider a transaction rollback. Oh wait, this is not SQL Server. User should verify all of the records are in the file. Could make a count of records made and show the user the information in a msgbox? |
Home > StuffLearned >