Search results for query: *

I'm running a VB6 app (SP3) with Access 2000, using Crystal Reports 7.0 for the report output. The system works perfectly on my development PC and on one workstation belonging to my client. Three other workstations are unable to run reports, as the errors listed below keep coming up, despite...

Steve Brock, Although your file may have a PIF extension, it seems to me from your description of its behavior that it's not actually a PIF file in the standard sense; i.e., as a Program Interface File for DOS applications. To check, click on the file and look at properties. Under...

It's difficult to recover corrupted memo data, but often the problem is related to incorrect pointers in the DBF memo field to the DBT data, which is stored in 512-byte blocks. There is an extremely handy, easy-to-use utility called DBTCHECK which actually does a more thorough job of cleaning...

Sorry, but PIF files are binary files, and you risk damaging one if you use a text editor. You should only use the Windows PIF editor (i.e., PIF properties features) to modify a PIF file. With respect to specifying the CONFIG.SYS, to my knowledge, Windows selects the CONFIG.SYS by default, and...

Yunta, The size limit for a DBT file is 32MB, which means that the file becomes highly unstable once it exceeds that size. There are a number of things that can be done to correct this. The first is to pack the DBF (best done by a copy for .not. deleted() to a new file). An excellent (and...

Yunta, The size limit for a DBT file is 32MB, which means that the file becomes highly unstable once it exceeds that size. There are a number of things that can be done to correct this. The first is to pack the DBF (best done by a copy for .not. deleted() to a new file). An excellent (and...