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

Problems moving from laptop to Desktop

P: n/a

I created and worked on my application on my desktop and copied it to
my laptop. After putting in many additions to the functionality on
the Laptop version, I copied it back to my desktop.

Nothing was changed on the desktop in respect of the configuration but
I now get an error which I am unable to fix.

I have a statement "Set cat = New ADOX.Catalog" This statement is
used in a number of places in my application but at the very first
time where this statement is to be executed, the following error

Run-time error '-2147024770 (8007007e)'
Automation erro
The specified module could not be found.

The following References (under Tools) are to be found checked on my
desktop and which is the same as in my laptop.

Visual Basic For Applications
Microsoft Access 9.0 Object Library
OLE Automation
Microsoft Activex Data Objects 2.1 Library
Microsoft ADO Ext. 2.6 for DDL and Security
Microsoft ActiveX Data Objects (Multi-dimensional) 2.5 Library
The only difference between my desktop and my laptop seems to be the
login Id.

in the Laptop, I am logged in as user "Administrator" while in my
desktop I am logged in with my name - although with (I am not sure!)
Administrator Rights.

I created the database on my desktop - when logged in with my personal
name. Then I moved the application to my laptop and modified it
extensively when logged in as User "Administrator". Now I am moving
it back to my desktop where once again I am logged in my personal name
- and the problem is occurring.

Both are standalone machines and do not belong to any LANs.

Thanks in advance.



Can any one help me solve this problem?
Nov 12 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.