Jack and Pat
drawbridgej at sympatico.ca
Sat Nov 19 08:12:09 CST 2011
Dan, Further to my (off list) note from late last night, I did a little more review. I opened the EIasT.mdb with a breakpoint to allow stepping thru the code. In the problem data base, the queries and forms - up to the problem form - are all exported as text as expected. After the error, the code stops on a STOP statement, as it should. If I step through, it continues with the next procedure in code and does Import the text that was previously exported. It seems I have a corrupted Form and that its source can not be retrieved. I did not find any resolution to the "there isn't enough memory to perform this operation. Close unneeded programs and try the operation again". Seems the consensus is to rebuild the form involved. So from an EIasT view, I did use the utility against another database and all was well. It did build a directory and saved all queries, forms, reports and nodules (I don't have any macros), It did import all the text. It does Compact and Repair. And the database , original and rebuilt are available. Good stuuf. I'm impressed with your code. No wasted code; very concise. I especially like the line numbers in the vba. I take it that is based on your use of FMC utilities. The progress bars are a nice feature - seems there are lots of people trying to build these based on forums I've seen. Again, thanks for responding quickly, and thanks for the EIasT code. Perhaps it should be made available at databaseadvisors as a utility. Jack