Bob --

You may have discovered that there are several operations that will bloat a DBC. Case in point -- when a CREATE SQL VIEW statement is fired, it APPENDs rows to the DBC that describe the view. If you ever fire the same CSV over again, the "old" view's rows are deleted from the DBC, and the "new" view's rows are APPENDed to the end.

So what you end up with is a whole bunch of deleted records lurking around in the DBC. To see for yourself, do this:

USE MyDB.dbc EXCLUSIVE
BROWSE

While you have the DBC opened EXCLUSIVEly (as above), you can eliminate the bloat by PACKing the DBC, just like you might PACK any ordinary DBF.

Bill

PS -- Just to be on the safe side, back up the entire database before you PACK the DBC.

>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!