P
Pieter Wijnen
Well,
it's a long time since I've actually posted a question...
I have a runtime installation of Access '97 (several frontends, several
backends - all secured + common "tools" mde)
I have made sure that all dll's , ocx'es etc are up to date
I have included an erata about how to install on Office 2000 systems
the problem is common to both win 2000 & xp
the problem is common to both full version of '97 & runtime
I've changed the extension of my db's to avoid '97 to "steal" .mdb from the
clients version of access (if any)
The problem is that when installed on a client machine (not on all
machines - but far to often) access crashes immediately
the problem disappears however if the client opens Access & open any db
(secured or not) from the file menu - which is not supported with the
runtime installation
the two things I haven't tried yet (but why post if I haven't missed
anything ... ) are
1) put the Databases in a decompiled state on the distribution CD
2) tried a runtime shortcut to an unsecured database (ie ommitting the
/WRKGRP switch)
My guess is offcourse that it has to do with Access modifying the registry
(as it does) on opening & that things happen in parallell when you provide
all switches (!?!)
any ideas will be appreciated
--
Pieter Wijnen
When all else fail try:
http://www.mvps.org/access
http://www.granite.ab.ca
http://allenbrowne.com/
it's a long time since I've actually posted a question...
I have a runtime installation of Access '97 (several frontends, several
backends - all secured + common "tools" mde)
I have made sure that all dll's , ocx'es etc are up to date
I have included an erata about how to install on Office 2000 systems
the problem is common to both win 2000 & xp
the problem is common to both full version of '97 & runtime
I've changed the extension of my db's to avoid '97 to "steal" .mdb from the
clients version of access (if any)
The problem is that when installed on a client machine (not on all
machines - but far to often) access crashes immediately
the problem disappears however if the client opens Access & open any db
(secured or not) from the file menu - which is not supported with the
runtime installation
the two things I haven't tried yet (but why post if I haven't missed
anything ... ) are
1) put the Databases in a decompiled state on the distribution CD
2) tried a runtime shortcut to an unsecured database (ie ommitting the
/WRKGRP switch)
My guess is offcourse that it has to do with Access modifying the registry
(as it does) on opening & that things happen in parallell when you provide
all switches (!?!)
any ideas will be appreciated
--
Pieter Wijnen
When all else fail try:
http://www.mvps.org/access
http://www.granite.ab.ca
http://allenbrowne.com/