Joel, a couple of comments. Most of us RELOAD rather than PACK our databases. PACK, when it fails, can leave you with an unusable database. RELOAD allows us to retain the original and create a new database. As a side benefit, RELOADing a database performs logic much the same as defragmenting a disk drive: it makes all the rows of a table contiguous, resulting in a bit faster retrieval, we hope.
If you RELOAD your database, you will find one or more tables that come up short because of corruption in a row of data. In worst case scenarios, the procedure abends at the bad row and does not complete the remaining tables, nor the indexing. You can log all the error messages to a file when reloading by writing a short command file such as the following: OUTPUT MyReload.log WITH SCREEN -- the last allows you to watch the procedings CONNECT mydatabase RELOAD mynewdatabase DISCONNECT OUTPUT SCREEN RBEDIT MyReload.log --- Joel Solomon <[EMAIL PROTECTED]> wrote: > When I try to pack my database I get the following error > > > Packing data for VARCHAR and VARBIT columns > -ERROR- Disk problems - Please check disk and files. (2036) > > What is the problem and how can I fix it? > > Joel Solomon > Controller > Barbizon International > [EMAIL PROTECTED] > > ===== Albert Berry Management Consultant RR2 - 1252 Ponderosa Drive Sparwood BC, V0B 2G2 Canada (250) 425-5806 (250) 425-7259 (708) 575-3952 (fax) [EMAIL PROTECTED]
