Automation Error -2146500594 (800f000e)

[robs23]

Hi Guys,



A database I've created for the company I work at doesn't work on 1 workstation. It runs correctly on other (about 20 workstations).
This 1 user is getting automation error 800f000e at loading start form. The starting code seems to work correctly, but during its runtime some forms are called and they give the error.
I gave it additional testing and even if I load 1 form (it loads correctly) that has several textboxes and button, it gives me this error when I run Forms(myFormName).Name from immediate window. The form is open when I check it from immediate window and it should produce proper name (it does so on other WS).

I've already tried:

• Compact & Repair - no result
• Compiling - no result
• importing all object to new database and running it - same story
• checking all references - none are missing

What is going wrong here? During start-up this database runs successfully some complicated code (e.g. mapping network drive, linking to back end or injecting new keys to registry) and then crashes at rather very simple form.

All ideas are very welcome!

Robert

[CJ_London]

one other thought - are the SP's up to date on the failing machine?

[robs23]

You mean Windows' service pack or Office service pack?

[CJ_London]

all or any

[ranman256]

I've had this too. It works on all PCs but 1.
SOMETHING, a driver, or update is different there than the others.

[robs23]

Have just checked and he (the guy that is having the issue) runs the very same version of Office/Access/Operating system. It includes also service packs. In other words we have exactly the same configuration. What else might be going haywire?

@ranman256 I didn't check whether the drivers are the same but I hope I won't have to


Robert

[CJ_London]

you say you have compacted, decompiled - have you done that on the rogue machine?

Also do all your modules (including form) use Option Explicit? If not, add it in and compile

you say 'database runs successfully some complicated code (e.g. mapping network drive, linking to back end or injecting new keys to registry)'

Is this working OK on the rogue machine? in particular the registry update - perhaps user rights are slightly different?

Only other thought is, in the rogue machine to build the problem forms from scratch, testing as you go

[robs23]

Hi Guys,

@Ajax I've checked his registry and all is fine


Sorry for no contact for 2 days, I haven't been able to check everything. Attached is a db with login form and "Create user" form. They are imported from my main database. Whole code needed is also included in module1. When you open the database, "frmStart" starts and open "frmLogin" form. There you click on user you'd like to log in on and click "Zaloguj" (or just double-click on user). Form "frmHaslo" will pop-up asking for your password (password for all "users" is "xxx"). When you type the password in and hit ENTER, a message "logged" should pop-up. It works perfectly well here, on malfunctioning workstation it opens "frmStart" and is opening "frmLogin" but gets stuck there looping.
Another good example is "frmDodajUsera" that allows you to create new user. Here it works perfectly well, on his WS you get error "The expression On Click you entered as the event property.." after clicking "Dodaj" (doesn't matter if textboxes are filled in or blank).


For me it's clear indication his set up is broken. Access installation needs to be done. BTW. can he reinstall Access without reinstalling whole Office?


Robert

[CJ_London]

I'll take a look later - you can just reinstall access, not the whole office suite

[robs23]

Hi Guys,


Topic can be closed - it turned out that there wasn't "Polish" language set for non-Unicode programs in "Region & lanugage". Stupid really.
Many thanks for your support!


Robert