Solved

Pb linked serevr between SQLSERVER 2005 and ACCESS 1997

Posted on 2008-06-16
7
619 Views
Last Modified: 2010-04-21
We have an available connection between SQLSERVER 2005 and a converted ACCESS database from 97 into
ACCESS 2003.
We exeperience a problem for what concerns the linking if ACCESS 97 is not converted.

The problem is we cannot convert ACCESS database on production because a lot of users use ACCESS 97

If an microsoft expert could help we would enjoy so much here is the error message.


Le fournisseur OLE DB 'Microsoft.Jet.OLEDB.4.0' du serveur lié 'access' a retourné le message 'Impossible de démarrer votre application. Le fichier d'informations du groupe de travail est absent ou ouvert en mode exclusif par un autre utilisateur.'.
Msg 7399, Level 16, State 1, Line 1
Le fournisseur OLE DB 'Microsoft.Jet.OLEDB.4.0' du serveur lié 'access' a rapporté une erreur. Échec de l'authentification.
Msg 7303, Level 16, State 1, Line 1
Impossible d'initialiser l'objet de la source de données du fournisseur OLE DB 'Microsoft.Jet.OLEDB.4.0' du serveur lié 'access'.

Best David
0
Comment
Question by:davidgfi
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 50

Expert Comment

by:Gustav Brock
ID: 21797570
Did you follow the advice in BOL regarding this?

As stated here:
http://www.experts-exchange.com/Software/Industry_Specific/Financial/Simply_Acct/Q_23321583.html

/gustav
0
 

Author Comment

by:davidgfi
ID: 21810896
Hi Gustav,

I've looked at the advice in BOL.
I've showed it to my Director and he tried to understand with me but he says it is not that the problem.
It is just how to create a linked server from SQL SERVER 2005 and ACCESS 97.

Best David
0
 
LVL 50

Expert Comment

by:Gustav Brock
ID: 21810989
Then you may need to rephrase your question. What is linking to what and what version(s)?

Is it just an Access 2003 frontend attached to tables in an SQL Server?

/gustav
0
Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

 

Author Comment

by:davidgfi
ID: 21812496
gustav

The database is SQLSERVER 2005 on which we do some query.
For this operation we need data which are on another computer in the Local ARea Network.
Those data are stored in ACCESS 97.
So it is not Access 2003 frontend with SQLSERVER.
It is stored procedure on SQLSERVER 2005 which need data from ACCESS 97.
The solution we tried was to create a linked server to ACCESS 97 to read the data we used Jet.

Maybe that now the question is easier to understand.
Sorry for the vocable but I am french and I do my best to try to explain.

Thank you for yor help.

David
0
 
LVL 50

Accepted Solution

by:
Gustav Brock earned 500 total points
ID: 21812902
OK, but for the linked server the error message you receive (in French) is similar to the message here:

http://www.experts-exchange.com/Software/Industry_Specific/Financial/Simply_Acct/Q_23321583.html#a21370281

Quote:

That's with the registry change, and without the registry change, I get;
    OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "SADataJET" returned message "Cannot start your application. The workgroup information file is missing or opened exclusively by another user.".

Even if the advice in the BOL is followed, I have had troubles connection the mdb file. In those cases I manage by granting user Admin of the workgroup file to have full access and no password. Access (JET) will use Admin as the default user name when no workgroup file is found.

/gustav
0
 

Author Closing Comment

by:davidgfi
ID: 31467492
Th&ank you very a lot to have explain better.
In the other question it was difficult for me to transalte
Best David
0
 
LVL 50

Expert Comment

by:Gustav Brock
ID: 21813383
You are welcome!

/gustav
0

Featured Post

MIM Survival Guide for Service Desk Managers

Major incidents can send mastered service desk processes into disorder. Systems and tools produce the data needed to resolve these incidents, but your challenge is getting that information to the right people fast. Check out the Survival Guide and begin bringing order to chaos.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Access custom database properties are useful for storing miscellaneous bits of information in a format that persists through database closing and reopening.  This article shows how to create and use them.
This article describes a method of delivering Word templates for use in merging Access data to Word documents, that requires no computer knowledge on the part of the recipient -- the templates are saved in table fields, and are extracted and install…
Familiarize people with the process of utilizing SQL Server views from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Access…
Basics of query design. Shows you how to construct a simple query by adding tables, perform joins, defining output columns, perform sorting, and apply criteria.

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question