Charlotte Foust
cfoust at infostatsystems.com
Tue May 4 16:52:23 CDT 2004
Yes we do. However, we had inadvertently let an internal installer go
with Office Web Components (or whatever the reference is) included,
since Access XP includes that by default when you build a new database.
It isn't needed and we took it out, but it caused a problem when the
setup was created on a machine that also has O2003 installed (though not
Access 2003) and the installation was run on a machine with 2002
installed.
Charlotte Foust
-----Original Message-----
From: Doug Murphy [mailto:dw-murphy at cox.net]
Sent: Tuesday, May 04, 2004 1:06 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Msado15.dll and Sqloledb.dll overwritten
makesAccessdbcrash
Hello Charlotte,
Your comment re having problems with your installer is disturbing. Do
you use the runtime files provided by Sagekey?
Doug
Douglas Murphy
Murphy's Creativity
(619) 334-5121
doug at murphyscreativity.com
www.murphyscreativity.com
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte
Foust
Sent: Tuesday, May 04, 2004 1:52 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Msado15.dll and Sqloledb.dll overwritten makes
Accessdbcrash
The ADO version is the one installed with Jet SP-8 and with Office 2003.
Do you happen to have 2003 on one of your own machines? We've had a few
odd surprises when an AXP installer was built on a machine with O2003
installed, even though we use Wise and SageKey.
Charlotte Foust
-----Original Message-----
From: Greg Smith [mailto:GregSmith at starband.net]
Sent: Tuesday, May 04, 2004 11:41 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] Msado15.dll and Sqloledb.dll overwritten makes Access
dbcrash
Hi everyone!
I have an odd situation with a client who has an Access XP database FE
with a linked SQL BE, running on WinXP, SP1.
I didn't write the Access App, so I'm coming into this cold.
We installed an imaging application (File Magic, network version, 5 user
license) which uses MSDE.
Before install File Magic, his Access DB was working just fine. The two
files and versions are:
FileName Ver Before Ver After
Msado15.dll 2.71.9030.0 2.80.1022.0
Sqloledb.dll 2000.81.9042.0 2000.85.1022.0
After installing File Magic, it works, but the Access DB links to the
SQL BE are hosed.
Obviously File Magic is installing newer versions of these files over
the older ones, but what the heck could cause it to hose up the Access
db's links?
If you keep a copy of the older files, then, after installing File Magic
but before rebooting, copy the older ones OVER the newer ones, then
reboot...BOTH apps work just fine.
Has anyone ever seen this before? Or am I out there on the edge
again....bleeding profusely once more?
Btw, the File Magic techs haven't heard of anything like this before. If
it wasn't a result of a problem INSIDE File Magic, they have no clue.
Any enlightenment would be greatly appreciated!
TIA.
Greg Smith
GregSmith at Starband.Net
--
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com