Support Forums - View Thread

View Thread

The following is the text of the current message along with any replies.

Messages 1 to 2 of 2 total

Thu, Nov 19 2009 2:29 AM	Permanent Link
Peter	Hello I reverse engineered a database with 140 tables, and some of those contain a few thousand records. When I try to run the script, using an EDBScript component, the script stops at line 2,578 (of 233,830). Is there a way around this limitation? Would a Procedure handle such a large file? I am using EDB 2.4 ANSI. Regards & TIA Peter
Fri, Nov 20 2009 2:24 PM	Permanent Link
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com	Peter, << I reverse engineered a database with 140 tables, and some of those contain a few thousand records. When I try to run the script, using an EDBScript component, the script stops at line 2,578 (of 233,830). Is there a way around this limitation? >> Not really, the scripts are not intended to be used as a replacement for large data imports. You should export the source tables and then use an IMPORT TABLE statement to bring in the data instead, leaving the script to deal only with the data-definition. -- Tim Young Elevate Software www.elevatesoft.com