Access Backwards Compatibility

[generallyconfused]

Hello all,

I've developed a little access application for my boss in Access 2002. He is operating in Access 2000. I have the default file format set to 2000 in my version of 2002. And the dbase works great for me in 2002.

My problem is when I send him a copy of the dbase to look over, the visual basic editor pops up on him all the time when opening forms. According to his account it's not the Error with End or Debug, it's the actual editor that is just opening without warning. I had him look for missing references but all the refs appear to be there. So I'm confused, a little more than generally at the moment.

Is this a backwards compatability issue? Or does he have something turned on in his install of Access 2000 that might be causing this? There is a lot of vb in this app, and I'm not a programmer, I'm a mechie actually. So maybe all my dirty and inefficient scripts are causing this?

Any help would be greatly appreciated. Thanks in advance!

 

[RoyVidar]

Hi!

I've found the same irritating thing (and no errors here either). Found out that where the yellow line appeared, was at lines I've had breakpoints on.

After that, I always clear all brekpoints, debug | compile, compact & repair, and it seems to work.

If anyone has more info, I'd also appreciate it.

Roy-Vidar

 

[generallyconfused]

I had him check for breakpoints and watches and none existed in the module.

I did find out there is a difference in our references. My version references the Access 10.0 Object library while his references the Access 9.0 Object Library. Could this be the source of my woes?

If so, is it possible to export all my refences with my dbase?, or perhaps it is possible to download that object library from the net? Hopefully it won't require an upgrade to Access XP.

In searching the net I came across a few references to .NET architecture also so I've asked him to make sure he has the .NET items from Windows Update installed.

Crossing my fingers. Thanks for your help Roy!

 

[RoyVidar]

Hi again!

As I stated, I don't know anything about what's causing this, so I hoped some more knowledgeable people join in. But I'll elaborate some more on my "advice".

I have a similar situation, where I have developed a system in 2002, and my client uses 2000. From time to time he calls and want's something added to the functionality. When programming and testing, I tend to set breakpoints here and there - on my computer, in my version of Access... As I've understood it, those breakpoints SHOULD all be cleared when exiting a database, and definately, when opening the database on another computer. But what I've experienced, is the same as you, my client on the phone stating there's a yellow line on "some white background" with "uncomprehensable lyric" (VBA Editor) (actually, most of what he says isn't quotable here). Those lines are either lines I remember having set breakpoints on in my code or they are lines where I've stopped debugging manually and corrected errors.

I've found that when I remove all breakpoints in MY code/on MY computer, use Debug | Compile + save, and the Compact & repair, BEFORE I send it, this behavior does not occur ('cept sometimes when, in rush, I haven't been completely accurate with my error handling, it shows up again, but then ONLY on error) I don't know why, but am quite happy since it works;-)

(I've been with my client, experiencing this, and no, there are no breakpoints in his code, neither should one exist, but, to me, it seems they, for some reasons, are "remembered" in the db, and Access halts at them)

The references:
Office 2000 is version 9.0 and Office 2002 is version 10.0, so the "changes in references" is as it should be. Only 9.0 references are available in 2000 (unless other tings are installed wich Office might reference).

If the references was causing this, I think you would either have got a message stating, or would have seen it in the Tools | References:
"Missing/invalid reference..."

And yes, I think that to avoid this completely (not having to deal with it), one of you probably might consider changing versions, but do try out what I've posted, you might share my luck;-)

Anyone else have some advice?

Roy-Vidar

 

[generallyconfused]

Thanks for all replies.

The problem was a lack of MDAC 2.7. Or installing MDAC 2.7 fixed an problems my boss was experiencing.

Thanks again!