Logging break in connection to Back-End

[twinnyfo]

SP,

Programatically , yes:

Option Compare Database
Option Explicit

Public Function _
    CompactDB( _
        strSrc As String, _
        strDest As String) _
    As Boolean
On Error GoTo EH

    CompactDB = Application.CompactRepair(SourceFile:=strSrc, _
                                          DestinationFile:=strDest, _
                                          LogFile:=False)

    Exit Function
EH:
    CompactDB = False
    Exit Function
End Function

Depending upon your network security protocols, this may require monitoring during execution. The theory here (to make sure you don't lose any data) is to follow these steps:

1. Make a copy of your BE
2. Compact your BE to a new file name
3. Rename that file to overwrite the original BE

When I have corrupt data, I prefer to grab the BE and save it locally and perform manual compact and repair--simply because my local machine can do this much faster than trying to do it over a network (or even over PVN which is horrendously slow for us).

"In theory" this should help alleviate some of the problems. But, I can't guarantee anything. :-)

Hope this hepps!