P
Patrick
Probably I am not the first with that problem...
PC's running Office XP on NT 4.0 (SP6a). We have got
third-party MS Access 97 (!) developements and they
delivered .mde, not convertible/upgradeble in Access XP.
I installed beside Office XP a run-time version of Access
97 to get run the third-party apps. I have written a .cmd
to call that .mde with Access 97 explicitly. Funny, after
the application run, all the Access related association
are changed default to Access 97. That is, any non-access-
97 databases we have got to "open with..." MS Access XP.
This works fine, unless you run a Access 97 (the thirt-
party .mde) then it got changed back again. I could
include some registration code to the .cmd to change back
the .mdb, .mde... association on HKLM to MS Access XP
when the third-party .mde got closed.
This all is pretty wired, isn't it.
Got somebody nice and cool hints out there?
thx a lot
PC's running Office XP on NT 4.0 (SP6a). We have got
third-party MS Access 97 (!) developements and they
delivered .mde, not convertible/upgradeble in Access XP.
I installed beside Office XP a run-time version of Access
97 to get run the third-party apps. I have written a .cmd
to call that .mde with Access 97 explicitly. Funny, after
the application run, all the Access related association
are changed default to Access 97. That is, any non-access-
97 databases we have got to "open with..." MS Access XP.
This works fine, unless you run a Access 97 (the thirt-
party .mde) then it got changed back again. I could
include some registration code to the .cmd to change back
the .mdb, .mde... association on HKLM to MS Access XP
when the third-party .mde got closed.
This all is pretty wired, isn't it.
Got somebody nice and cool hints out there?
thx a lot