Yeah, I added a PACK to the application. Since I don't have access to the machine (except through the WEB and Enterprise Manager) I had no idea that the DBC was growing so fast. Normally I don't have a need to add/delete objects in a database. I should have realized it, but it was a big surprise!


>Bob,
>
>USE TheBigA**DBC EXCLUSIVE
>PACK
>
>You are just suffering from the bloat of deleted records of earlier versions of tables, views etc. still being in the DBC.
>
>You should consider using a TEMP.DBC to hold these temp definitions.
>
>
>>There is no point to this message other than for those who might be curious on how big a DBC can be.
>>
>>Well, I have one that has ONE table, and six remote views and one remote connection defined.
>>
>>This DBC and the exe that uses it loads data (after cleaning it up) from some oddball DBF's (one dbf has 305 fields) into SQL Server. This happens every night.
>>
>>Because I drop the table, recreate it, drop the connection, recreate it, etc. The DBC kept growing and growing and growing. I didn't know about this until the user complained that they were running out of HD space and needed a new 28 GB drive.
>>
>>The DBC was about 1.1 GB in size. Yes, that is GIGABYTES. The DBC file was over 1 GB and the other files (DCT, DCX) added a few measly MB.
>>
>>I was quite amazed, although in a few weeks it would probably have reached the 2 GB limit.
>>
>>So I think I am safe in saying My DBC is bigger than your DBC!