| Andy G 2005-04-06, 8:05 pm |
| I agree 100% with 'sjl'!!!! The reference problems with a2000 to a2003 is a
pain. Either dropping references and access trying to be too smart and
adding them. I have a2003 installed on my machine (along w/ a2000 and a97)
and any time I try to open a a2000 database using my a2000 version it picks
up new references from the a2003 version. References are ALWAYS a big issue
in coversion, and anyone that tells you different hasn't had the experience
w/ the problems or is in reference denial.
"sjl" <noemail@email.com> wrote in message
news:%23$DqBReDFHA.228@tk2msftngp13.phx.gbl...
> Albert,
> The primary issue I am having relates to the MS Access Object Library.
> I'm developing a 2000 version db on a 2002(XP) machine. When I compile my
> app, its referencing the 10.0 Object Library. When I ship that to my
> client, that library doesn't exist and the reference automatically
> switches to the 9.0 Object Library. However, in doing so, nothing works
> until the app is compiled using 9.0.
>
> As you stated, I have found that compiling my app on a A2000 machine
> pointing to 9.0 prior to delivery solves the problem. I'm just wondering
> if this is a required step or is there any way to accomplish this on my
> A2002(XP) machine prior to delivery? The user doesn't have the 10.0
> Object Library. They only have A2000 (9.0). It sounds like regardless of
> whether I want to distribute a locked down .mdb file or an .mde file, I
> still have to have an instance of A2000 to do a final compile on before
> distribution?
>
> Thanks,
> sjl
>
> "Albert D. Kallal" < PleaseNOOOsPAMMkalla
l@msn.com> wrote in message
> news:%23p1IPocDFHA.2824@tk2msftngp13.phx.gbl...
>
>
|