dbTalk Databases Forums  

Strange compile problem using me. keyword - Access 2010

comp.databases.ms-access comp.databases.ms-access


Discuss Strange compile problem using me. keyword - Access 2010 in the comp.databases.ms-access forum.



Reply
 
Thread Tools Display Modes
  #11  
Old   
David W. Fenton
 
Posts: n/a

Default Re: Strange compile problem using me. keyword - Access 2010 - 08-28-2010 , 02:10 PM






exebat <srdjan.vasiljevic (AT) gmail (DOT) com> wrote in
news:93c0d151-756d-43ce-bd22-8dfc0d80eb1d (AT) t2g2000yqe (DOT) googlegroups.com
:

Keep the references with the * and lose the rest:

Quote:
Here is my reference list:

*Visual Basic For Applications
*Microsoft Access 14 Object Library
Ole Automation
*Microsoft Office 14 Access Database Engine object
Microsoft HTML object library
Microsoft WMI Scripting V1.2
Microsoft Scripting Runtime
Microsoft Windows Common Controls 6.0 (SP6)
OLE Automation provides no useful functionality, and is just a
default reference. If you are not convinced that it's not useless,
browse it in the object viewer, and you'll see there is simply no
justification for it in 99% of databases.

All the others except the latter can be used with late binding (and
should be, in my opinion).

You should consider what you're using the last one for -- if it's
for File Open dialogs, you can easily get rid of it and use the
built-in FileDialog, with no reference needed.

I don't believe any of this will resolve your problem (I think you
have corruption), but it will make for a better, more stable
database that will be prone to fewer problems on different PCs
(where installations can vary and references can break easily).

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

Reply With Quote
  #12  
Old   
Douglas J. Steele
 
Posts: n/a

Default Re: Strange compile problem using me. keyword - Access 2010 - 08-28-2010 , 03:42 PM






You can't have both references.

If you're using an MDB, you use the DAO 3.6 reference,

If you're using an ACCDB, you use the Access Data Object Enginer reference.

--
Doug Steele, Microsoft Access MVP
http://www.AccessMVP.com/DJSteele/AccessIndex.html
Co-author: "Access 2010 Solutions", published by Wiley
(no private e-mails, please)


"Salad" <salad (AT) oilandvinegar (DOT) com> wrote

Quote:
exebat wrote:

I reinstalled Access, created new database and imported all over
again. I no longer have the Me. problem, but I still have the "Invalid
database Object reference".

When I copy the database to any other computer I get this error, and I
cant do anything until I do "Compact and repair". Since my software
uses automatic updating, it is a really big problem for me.

What happens if you move DAO3.6 ref above the ref for Microsoft Office 14
Access Data Object Engine.

Why don't you list your references and the order?

Reply With Quote
  #13  
Old   
exebat
 
Posts: n/a

Default Re: Strange compile problem using me. keyword - Access 2010 - 08-29-2010 , 05:40 AM



I tried Decompile an it doesnt work.

I also tried to import everything in the new database except the
startup form, and recreate that form and it did not help.

If I do compact and repair all works well.

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.