Microsoft KB Archive/221666

= FIX: The Save Generated SQL option in the SQL Upsizing Wizard causes the Script.fpt file to become very large in Visual FoxPro for Windows 5.0 and in Visual FoxPro for Windows 6.0 =

Article ID: 221666

Article Last Modified on 3/10/2005

-

APPLIES TO


 * Microsoft Visual FoxPro 5.0 Standard Edition
 * Microsoft Visual FoxPro 5.0a
 * Microsoft Visual FoxPro 6.0 Professional Edition

-



This article was previously published under Q221666



SYMPTOMS
You use the Visual FoxPro SQL Server Upsizing Wizard to upsize a database to SQL Server. You select the Save Generated SQL option in step 7 of the wizard. When the generated SQL code is saved to the Script.dbf file, the memo file Script.fpt will grow to a very large size. This may be on the order of hundreds of megabytes. Issuing a PACK MEMO on Script.dbf will cause the size of the memo file to be reduced by a factor of about 1000.



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

This bug was corrected in Visual Studio 6.0 Service Pack 3.

For more information about Visual Studio service packs, please see the following articles in the Microsoft Knowledge Base:

194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why

194295 HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed



Steps to Reproduce Behavior
 Make a new directory and set it as the default directory within Visual FoxPro. You will need 200+ MB free on this drive.  Run the following code from a program (.PRG) file. It creates a DBC with 200 10-field tables, with relations between each table and the next and indexes on all the fields: SET SAFETY OFF SET TALK OFF CLEAR CLOSE DATA ALL CREATE DATABASE testdb FOR lni = 1 TO 200 CREATE TABLE ('thisisthetabname'+ALLTR(STR(lni))) ; (('FieldName1') C(10) NOT NULL PRIMARY KEY, ;     ('FieldName2') C(10) NOT NULL, ;      ('FieldName3') C(10) NOT NULL, ;      ('FieldName4') C(10) NOT NULL, ;      ('FieldName5') C(10) NOT NULL, ;      ('FieldName6') C(10) NOT NULL, ;      ('FieldName7') C(10) NOT NULL, ;      ('FieldName8') C(10) NOT NULL, ;      ('FieldName9') C(10) NOT NULL, ;      ('FieldName10') C(10) NOT NULL) IF lni > 1 ALTER TABLE ('thisisthetabname'+ALLTR(STR(lni-1))) ; ADD FOREIGN KEY TAG ('FieldName1') REFERENCES ; ('thisisthetabname'+ALLTR(STR(lni))) TAG ('FieldName1') ENDIF FOR lnj = 2 TO 10 lcExpr = 'FieldName'+ALLTR(STR(lnj)) INDEX ON &lcExpr TAG ('fldname'+ALLTR(STR(lnj))) ENDFOR ENDFOR  Run the SQL Server Upsizing Wizard. Select the DBC you created above in Upsizing Wizard step 1, and then click Next. In step 2, select an ODBC datasource to a SQL Server you can upsize to. Log on and then click Next. In step 3, select all of the tables, and then click Finish.</li> In step 9, click the Save Generated SQL option, then click Finish again.</li>  After Upsizing Wizard has completed, execute the following commands from the Command window: DIR upsize\script.fpt USE upsize\script EXCLUSIVE PACK MEMO DIR upsize\script.fpt RESULTS: Before the PACK MEMO command, the DIR command will return 206,797,184 bytes as the size of the Script.fpt file.

After the PACK MEMO command, the DIR command will return 201,472 bytes as the size of the Script.fpt file. </li></ol>

Keywords: kbbug kbfix kbdatabase kbwizard kbvs600sp3fix KB221666

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.