developing in ACC2000, production in ACC2003

[Mark]

All,

Our department is split, and some of us have ACC2000, others have ACC2003. I
use ACC2000 for the database development, but the people who use this
database use ACC2003.

What we've noticed is that the database needs to be repaired 3-4 times a
week. Other issues creep up that cause even bigger problems. Generally, we
backup the database nightly since on a couple occasions, it's been corrupted
beyond repair.

I want to make a case for everyone to use office 2003. My question is, can I
blame the need for repairing the database on that (using ACC2000 to develop,
and 2003 to use)? If so, are there any microsoft articles saying that using
both versions to access an .mdb isn't recommended?

 

[Van T. Dinh]

No, not really. Developed in A2000 and used with A2003 is fine. Basically,
you can't use new features of A2002 and A2003 in your development but the
database should work fine. A2000, A2002 and A2003 use the same JET version
also. In addition, the default database file format for A2000, A2002 and
A2003 is actually A2000 database file format.

There are a few things you must do, though:

1. Have you split the database application to Front-End and Back-End? For
multi-user application, you should (nearly must, actually) split the
application to Front-End and Back-End and each user should have a separate
copy of the Front-End.

2. Have you applied all Service Packs / Service Updates to your A2000
installation? The original A2002 was bugsy but this has been fixed by SPs /
SRs.

3. You should also check to make sure all installation use the latest JET
version (IIRC, JET 4 SP 8) and the latest ADO Library (IIRC, version 2.8) if
you use ADO.

 

[Mark]

It may seem weird, but getting 2 and 3 done won't be that easy. It has to go
through the IT team; I don't have the ability to do this for the department.
And unfortunately, I haven't split the FE and BE. There are remote users and
trying to keep everything at the same version (the database is constantly
being updated) would be tough if i split it apart.

As for it not being a problem, then I'm confused as to why I'm getting so
many "you need to repair the database" errors. This is the only database that
has these problems and this is the only database being accessed with ACC2000
and ACC2003. Is there something I'm not coding right?

Thanks, Van.
-Mark

 

[david epsom dot com dot au]

It may seem weird, but getting 2 and 3 done won't be that easy. It has to

go

On the in-house application I support, the entry form
turns bright red if the versions are not up to date.
Messages don't bother the users: they just click OK and
go on, but having the application change colour worries
them.

I've given sample code for Jet 4.0 and Access 2000, but
you could extend this to handle multiple versions.

(david)


'--------------
'David Graham. (david) Right to attribution retained.
'Watch for word wrap

Option Compare Database
Option Explicit
Const mcModuleName = "mdlRP_DLLCheck"
'2003/02/26 dlg
Private Declare Function GetFileVersionInfo& Lib "Version" Alias
"GetFileVersionInfoA" (ByVal FileName$, ByVal lptr&, ByVal lSize&, lpvData
As Any)

Public Sub gsbDLLCheck()
If ("4.0.8618.0" > gfn_GetVersion("msjet40.dll")) Then MsgBox "Warning:
MSJET40.dll is " & gfn_GetVersion("msjet40.dll") ' & ", not 4.0.8618.0"
If ("9.0.0.6620" > gfn_GetVersion("msaccess.exe")) Then MsgBox "Warning:
MSACCESS.EXE is " & gfn_GetVersion("msaccess.exe") ' & ", not 9.0.0.6620"
End Sub

Public Function gfn_GetVersion(FileName$)
'2003/02/26 dlg --minimalist version -- Right to attribution retained
Dim iBuf(0 To 99) As Integer

Call GetFileVersionInfo(FileName$, 0&, 200, iBuf(0))
gfn_GetVersion = iBuf(25) & "." & iBuf(24) & "." & iBuf(27) & "." &
iBuf(26) 'FILE VERSION

End Function
'-------------

 

[Van T. Dinh]

Mutiple users using the same combined database file is a recipe for
disaster, IMHO.

Make sure you keep regular back-ups, daily or more frequent if possible
until you can split the database.

You also mentioned remote users. How do they connect to the database? This
is also a big potential for corrupting the database since interrupted
connection is more likely for the remote connections. In addition, it is
likely to be very slow for the remote users, bordering on unusable.

Tony Toews has the free utility so that you can update the Client FE file
easily. See:

http://www.granite.ab.ca/access/autoFE.htm

HTH
Van T. Dinh
MVP (Access)