When I create a dts package with 2 access connections that use the same
system.mdw I get an error when I try to save the 2nd connection. The error
message is :

Cannot start your application. The workgroup information file is missing or
opened exclusively by another user.

How do I create multiple Access connections to different Access databases
that all share a common mdw file?
--
Jeff

In message <0604B2CE-5C15-4B62-BDF9-767899ECA30B (AT) microsoft (DOT) com>, Jeff
Grundy <jeffgrundy (AT) nospam (DOT) nospam> writes
I don't know the answer, but why not use the same connection. You can
have two icons for the same connection, just select "Existing
connection" when you add the second "icon", so it re-uses the underlying
connection object.


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

I can not use the same connection to access 2 different Access databases.

"Darren Green" wrote:

Hi Jeff,

It seems I could share the system.mdw with two or more mdb files in DTS
package. Make sure mdw file path was put correct correctly in Jet OLEDB:
System database Property.

Let me know whether it works or share me the detailed steps you do. More
detailed information, I believe, will make us closer to the resolution.

Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!


Sincerely yours,

Michael Cheng

Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---------------------------------------------------------------
Get Secure! - http://www.microsoft.com/security

This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

The path I entered into the Jet OLEDB: System database Property is correct.

When I set the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engi nes\systemDb to the path of
my Workgroup Information File (mdw) file it solves the problem. That key also
solved a problem I was having with linked servers connecting to an Access 97
database.

When I set that registry key on my Sql Server I was able to use a linked
server based on access 97 secured databases when I was logged onto the server
however when I used Enterprise Manager form a workstation I recieved the
error "OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0' IDBInitialize::Initialize
returned 0x80004005:". I then set that registry key on the workstation and I
was able to use the linked server.

If I were to deploy an application that uses a linked server based on an
Access 97 (Maybe all versions of access) secured database then each client
needs to have the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engi nes\systemDb value set to
the path of the Workgroup Information File (mdw).

""Michael Cheng [MSFT]"" wrote:

Hi Jeff,

Thanks for sharing this with us!


Sincerely yours,

Michael Cheng

Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---------------------------------------------------------------
Get Secure! - http://www.microsoft.com/security

This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!