By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
428,631 Members | 892 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 428,631 IT Pros & Developers. It's quick & easy.

How to compact & Repair Back-end from Front-end

P: n/a
Hi folks,

Somewhere, I recently saw an article header titled:

"How to compact and Repair a back-end Access db from the front-end
using VBA" or words to that effect.

Now that I need it, I cannot find it. Does anyone know were to find
such an article?

Thanks
Nov 13 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Lauren Wilson wrote:
Hi folks,

Somewhere, I recently saw an article header titled:

"How to compact and Repair a back-end Access db from the front-end
using VBA" or words to that effect.

Now that I need it, I cannot find it. Does anyone know were to find
such an article?

Thanks


dbEngine.CompactDatabase "PathToSource" "PathToDestination"

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 13 '05 #2

P: n/a
Lauren,

Are you still looking for a calendar report? Leave your email and I will
send you a screenshot of what I
have.

Access Resource

"Lauren Wilson" <no****@private.com> wrote in message
news:0l********************************@4ax.com...
Hi folks,

Somewhere, I recently saw an article header titled:

"How to compact and Repair a back-end Access db from the front-end
using VBA" or words to that effect.

Now that I need it, I cannot find it. Does anyone know were to find
such an article?

Thanks

Nov 13 '05 #3

P: n/a

Yes.

Send it to my partners: su*****@lmc.bz

Thanks
On Tue, 24 May 2005 13:11:22 GMT, "Access Resource"
<ac************@discussions.microsoft.com> wrote:
Lauren,

Are you still looking for a calendar report? Leave your email and I will
send you a screenshot of what I
have.

Access Resource

"Lauren Wilson" <no****@private.com> wrote in message
news:0l********************************@4ax.com.. .
Hi folks,

Somewhere, I recently saw an article header titled:

"How to compact and Repair a back-end Access db from the front-end
using VBA" or words to that effect.

Now that I need it, I cannot find it. Does anyone know were to find
such an article?

Thanks


Nov 13 '05 #4

P: n/a
Bri
Lauren Wilson wrote:
Hi folks,

Somewhere, I recently saw an article header titled:

"How to compact and Repair a back-end Access db from the front-end
using VBA" or words to that effect.

Now that I need it, I cannot find it. Does anyone know were to find
such an article?

Thanks


Lauren,

Rick has already mentioned the key piece needed but there are a few
things that you need to know about to make this work.

If the Backend is being accessed then the CompactDatabase method will
fail as it cannot get Exclusive use of it. Your code will need to trap
this error. Also, if your frontend maintains any attachments to the
backend (ie first form open opens a recordset on the backend to force
the backend ldb file to remain for the session - a known trick to
speedup FE-BE setups) you will need to have your code close them before
the compact (and I suppose reopen them after). In some situations, you
may need to 'unlink' the tables from the BE (test without first as it is
much easier to code). The newly compacted backend then needs to replace
the old backend. I usually leave it around as a backup (renamed). Below
my sig is a function I use as a starting place. I pass to it the name of
a table in the BE so it can get the name of the BE from its connection
string.

--
Bri

My code, watch for wrap.

Function Compactdb(TableName As String) As Boolean
On Error GoTo Err_CompactDB

'If Tables are always connected then use commented code
'Dim Connections() As String
Dim i, j As Integer
Dim tbl As TableDef
Dim stFileName

DoCmd.Hourglass True

stFileName = db.TableDefs(TableName).Connect
stFileName = Mid(stFileName, InStr(stFileName, "=") + 1)

'If Tables are always connected then use commented code
'i = db.TableDefs.Count
'ReDim Connections(i)
'j = 0
'For Each tbl In db.TableDefs
' Connections(j) = tbl.Connect
' If Left(tbl.Name, 4) <> "Msys" Then
' tbl.Connect = ""
' tbl.RefreshLink
' End If
' j = j + 1
'Next

DBEngine.CompactDatabase stFileName, stFileName & "TMP"
If Dir(stFileName & ".BCK") <> "" Then _
Kill stFileName & ".BCK"
Name stFileName As stFileName & ".BCK"
Name stFileName & "TMP" As stFileName
If Dir(stFileName & "TMP") <> "" Then _
Kill stFileName & "TMP"

Compactdb = True

'If Tables are always connected then use commented code
'j = 0
'For Each tbl In db.TableDefs
' If Left(tbl.Name, 4) <> "Msys" Then
' tbl.Connect = Connections(j)
' tbl.RefreshLink
' End If
' j = j + 1
'Next

Exit_Compactdb:
DoCmd.Hourglass False
Exit Function

Err_CompactDB:
DoCmd.Hourglass False
Compactdb = False
If Err.Number = 3356 Then
MsgBox "The database is currently being used by another User. " & _
"You can only Compact the Database if you are the only person " & _
"using it." & vbCr & _
vbCr & "Please try again later.", vbExclamation, & _
"Database in Use by Another User"
Else
MsgBox Err.Description
End If
Resume Exit_Compactdb

End Function

Nov 13 '05 #5

P: n/a

Thanks a lot Bri!
On Tue, 24 May 2005 17:33:11 GMT, Bri <no*@here.com> wrote:
Lauren Wilson wrote:
Hi folks,

Somewhere, I recently saw an article header titled:

"How to compact and Repair a back-end Access db from the front-end
using VBA" or words to that effect.

Now that I need it, I cannot find it. Does anyone know were to find
such an article?

Thanks


Lauren,

Rick has already mentioned the key piece needed but there are a few
things that you need to know about to make this work.

If the Backend is being accessed then the CompactDatabase method will
fail as it cannot get Exclusive use of it. Your code will need to trap
this error. Also, if your frontend maintains any attachments to the
backend (ie first form open opens a recordset on the backend to force
the backend ldb file to remain for the session - a known trick to
speedup FE-BE setups) you will need to have your code close them before
the compact (and I suppose reopen them after). In some situations, you
may need to 'unlink' the tables from the BE (test without first as it is
much easier to code). The newly compacted backend then needs to replace
the old backend. I usually leave it around as a backup (renamed). Below
my sig is a function I use as a starting place. I pass to it the name of
a table in the BE so it can get the name of the BE from its connection
string.


Nov 13 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.