Re: Problem With database on other computers

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Allen Browne (AllenBrowne_at_SeeSig.Invalid)
Date: 08/13/04 

Date: Fri, 13 Aug 2004 11:03:30 +0800

Hi Randy

1. References (again)
Firstly, see if you can uncheck the OLE and VB App Ext. libraries, and still
compile the code. If it works, there are 2 less that could be causing the
problem.

On the Win 98 machines that have the problem, uncheck the DAO library as
well. Save. Then go back in and select the MS DAO 3.6 Library again. That
has been known to solve the problem in some cases.

2. Service Packs
If that does not work, check if there is a difference in the service packs
applied to the different machinces. Whether Office XP or Office 2000, they
should be SP3 (shows in the Help | About screen). You also need to check the
version of msjet40.dll on the problem machines. It should be 4.0.8xxx.0. If
you don't see the 8, they need the JET 8 SP8 update.

3. Binary incompatibility between versions
You have some machines on Office XP, and some on Office 2000? Presumably the
mdb is in Office 2000 format. Although Access 2002 can work with the Office
2000 format mdb, the binary code (compiled) is different. If you generated
the mdb using Access 2002 and experience problems on the machines that use
Access 2000, this may help:
3.1 On the Office 2000 machine, decompile the database by entering something
like this at the command prompt while Access is not running. It is all one
line, and include the quotes:
    "c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
       "c:\MyPath\MyDatabase.mdb"
3.2 Compact the database.
3.3. Compile again (code window, Debug menu). 

-- 
Allen Browne - Microsoft MVP.  Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Randy" <kerspi@inreach.com> wrote in message
news:N92dnatyp_XZIobcRVn-vA@inreach.com...
>I did not find any missing references, the references I have are:  "Visual
> Basic for Applications, MS Acces 9.0 Object Library, MS DAO 3.6, Ole
> Automation, and MS Visual basics for Applications Extensibility"  Do you
> have any other Ideas..Thanks..Randy
> "Allen Browne" <AllenBrowne@SeeSig.Invalid> wrote in message
> news:u9sDm1IgEHA.644@tk2msftngp13.phx.gbl...
>> Probably references. See:
>>     http://members.iinet.net.au/~allenbrowne/ser-38.html
>>
>>
>> "Kerman SPI" <kerspi@inreach.com> wrote in message
>> news:TsmdnQYEU5XBAIbcRVn-rw@inreach.com...
>> >I have an Access 2000 database I developed on my computer with windows
> XP.
>> > The database works great on xp and windows 2000.  On some computers 
>> > with
>> > windows 98 and with my database installed, I am getting errors that i
>> > cannot
>> > duplicate on xp or 2000.  The database is very buggy  on some 98
> operating
>> > systems  (Pentium 2, 350 mhz). even though they also have access 2000
>> > installed.  I am getting error messages such as when I am creating a 
>> > new
>> > record, I get "you cannot execute this command" I cant even close out
> the
>> > form.  Or the debug screen pops up. With the following code 
>> > highlighted:
>> > "DoCmd.OpenReport strDocName, acPreview, , strWhere"  Does any one have
>> > any
>> > ideas?  This is driving me crazy.  Thanks...Randy
>> >
>> >
>> > Private Sub Preview_This_Field_Note_Click()
>> >
>> > Dim strDocName As String
>> > Dim strWhere As String
>> >
>> >    If Me.Dirty Then   'Save any edits first.
>> >        Me.Dirty = False
>> >    End If
>> >    If Me.NewRecord Then
>> >        MsgBox "Field Note Not Selected.  Please Select a Field Note To
>> > Preview"
>> >    Else
>> >    strDocName = "Inedible Notesheet"
>> >    strWhere = "[AnalysisID]=" & Me![AnalysisID]
>> >    DoCmd.OpenReport strDocName, acPreview, , strWhere
>> > End If
>> >
>> > End Sub

Relevant Pages

  • Re: Library Database
    ... in the same folder location as the front-end database when you ... set the reference and compile the front-end MDE, ... Two of the libraries also reference ... all of this by simply not using references, ...
    (comp.databases.ms-access)
  • Re: 2000/2003 Reference Problems
    ... If you use only the essential libraries: ... Decompiling is a separate issue to references. ... >> Then compact the database: ... >> Tools | Database Utilities | Compile. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Undefined datatype
    ... Both the ADO and DAO libraries have a Database item. ... You also may have to check out the library references ... If any of the selected references have "MISSING:" in front of them, unselect ...
    (microsoft.public.access.modulesdaovba)
  • Re: List of tables and fields
    ... So I reordered my libraries to match my ... ADO and DAO Library References in Access Databases ... you won't need to import the module and report into every database ...
    (microsoft.public.access.tablesdbdesign)
  • Re: BuildIn VBA functions in Access 2002
    ... it is more likely a references issue. ... external program and object libraries that provide functionality that may be ... modules may not be in the same location on different machines, ... If any of the selected references have "MISSING:" in front of them, unselect ...
    (microsoft.public.access.modulesdaovba)