error 2447... (but only for one user) STUMPED

[Carl_R]

We have a shared DB on the network (slipt front/back ends).

Everyone can use the DB seamlessly except one user, who receives the following error when they try and close a form (which has some code).


Error 2447:
There is an invalid use of the .(dot) or ! operator or invalid parenthesis
You may have entered an invalid identifier or typed parentheses following a null constant.

I have checked things like regional settings and these look the same as everyone else' - now I am completely stumped...

Any ideas would be appreciated.

 

[KenHigg]

Check your ref's

???
ken

 

[The_Doc_Man]

Ken is probably right but I'll amplify just a smidgen.

Your references are probably whacked out. You might well have a missing reference. The problem you see is not what it seems, though. You see, when a reference is whacked, not only does good code fail to work, but you can't even predict the error message by which it reports the failure!

Another factor (and I'm including this so others reading the thread will recognize the symptoms if they see it again) is its selectivity. See, the references are stored in your Windows registry. So what happens is that everyone has their own copy of the registry and it is therefore possible to have everyone have the exact same versions of Windows and Office, yet one will have a problem and the other one will not. 'cause registries are local to EACH WORKSTATION. So they are unique, user to user. (AND cannot effectively be copied to someone else's system 'cause they also are tied to hardware addresses in the network cards and such.)

So the only solution is to go into a code page ON THAT USER'S MACHINE and follow Tools >> References and see what references are marked MISSING. Resolve that (if you have any) and see if it works better.

Please re-post under this or a new topic if it ain't references.

 

[Carl_R]

Sorted

Thanks KenHigg and DocMan... spot on

Actually, it was hard to spot as there were no missing references. In fact, the user could do everything in the DB except one thing (auto email send via Lotus Notes).

There was a reference to DAO3.6 Object Library and looking at my PC (and others), this was DAO3.5.

So, I browsed to DAO3.5, selected it and that did the trick.

Thanks again.

Carl

 

[KenHigg]

"...if it ain't references."

Gotta luv it...

ken

 

[The_Doc_Man]

There was a reference to DAO3.6 Object Library and looking at my PC (and others), this was DAO3.5.

Which tells me the oddball terminal had an older version of Office on it. I'm not going to swear to versions, but I think DAO35 went out with Ac97 and DAO36 came in with Ac2K.

That'll do it every time, 'cause DAO changed slightly between versions and (for Ac2K) there IS no backwards-compatibility version of DAO. Unlike on Ac97 where you could use DAO2535 to handle backwards issues and current references. Typical of Microsoft - learn a lesson and then promptly forget it again. 'cause there's no money to be made on backwards compatibility to their tiny little brains.