Could not create an instance of OLE DB provider 'Microsoft.Jet

Thanks for the replies.I changed C: to C$ but I still get the same error.
The machineNameOnNetwork is my local computer name which is on the corporate
network.Where am i going wrong?
Thanks for your help.
"Omnibuzz" wrote:

> A few pointers. Don't know whcih one is applicable for you though
> 1. If you are accessing a network share ,then the account in which SQL
> Server is running should have access to that share.
> 2. Do not use C:, use C$ like this..
> \\machineNameOnNetwork\c$\Test.mdb;"
> Hope this helps.Is your machine shared on the network?
i.e.
Can you access c:\test.mdb from another PC?
Is the database also running on your PC?
"tech77" <tech77@.discussions.microsoft.com> wrote in message
news:993B9891-0894-4046-AB32-A098D36C0FAD@.microsoft.com...
> Thanks for the replies.I changed C: to C$ but I still get the same error.
> The machineNameOnNetwork is my local computer name which is on the
corporate
> network.Where am i going wrong?
> Thanks for your help.
>
> "Omnibuzz" wrote:
>|||Not the account in which you have connected to SQL Server.
The account in which the SQL Server Service is running should have access to
your machine and your folder.
Or the best way is to copy this file to a folder in your SQL Server and use
that path in the ODS.|||thanks Omnibuzz,Jim and Mark for your responses.
.The machine on which SQL Server is running might not have access to my
machine and my folder.Its on a remote server.
And I cannot configure that machine so it has access to my machine.
So I have to install SQL Server locally else I cant accomplish what I am
trying to do or is there some workaround?
thanks
"Omnibuzz" wrote:

> Not the account in which you have connected to SQL Server.
> The account in which the SQL Server Service is running should have access
to
> your machine and your folder.
> Or the best way is to copy this file to a folder in your SQL Server and us
e
> that path in the ODS.|||Create a share on your system, and put the mdb file in it. Enable the guest
account for your system, and give the guest user write permissions to the
file (both through-share, and NTFS if necessary).
You'll have to enable the guest account for it to work, because the SQL
server is more than likely running under the Local System context on the
system it resides on. Local System has no authority over the network, so whe
n
the SQL system tries to connect to you, it appears as guest.
Another method involves trusting the SQL server for delagation, but since
you said you can't modify it, it's not worth going into detail.
HTH
"tech77" wrote:
> thanks Omnibuzz,Jim and Mark for your responses.
> .The machine on which SQL Server is running might not have access to my
> machine and my folder.Its on a remote server.
> And I cannot configure that machine so it has access to my machine.
> So I have to install SQL Server locally else I cant accomplish what I am
> trying to do or is there some workaround?
> thanks
>
> "Omnibuzz" wrote:
>|||You can put the MDB on the database server, instead of your PC. Make it a
share if others need access to it.
You can put the MDB on a network server that the SQL Server account would
have access to.
You can grant the SQL Server account access to the MDB on your machine.
(the above two require proper network security, but should not be difficult)
You can drop the MDB database entirely and move the tables to SQL Server,
which is probably the best bet. If you absolutely need to access these
tables via MS Access, you can create linked tables pointing to SQL Server.
This will put all the tables local in SQL Server, but still let you use your
access front end.
Is there really a need to have SQL server access your local MDB, rather than
migrating the tables and data to SQL Server?
"tech77" <tech77@.discussions.microsoft.com> wrote in message
news:7B9F4484-F46C-493F-8830-A5602EC96B55@.microsoft.com...
> thanks Omnibuzz,Jim and Mark for your responses.
> .The machine on which SQL Server is running might not have access to my
> machine and my folder.Its on a remote server.
> And I cannot configure that machine so it has access to my machine.
> So I have to install SQL Server locally else I cant accomplish what I am
> trying to do or is there some workaround?
> thanks
>
> "Omnibuzz" wrote:
>
access to
use|||Finally it was decided to download SQL Server express edition 2005 and copy
the Access tables to SQL Server and use for our requirement .
Thanks all for your help.I learnt quite a few things from you all.
Regards,
tech@.77
"Jim Underwood" wrote:

> You can put the MDB on the database server, instead of your PC. Make it a
> share if others need access to it.
> You can put the MDB on a network server that the SQL Server account would
> have access to.
> You can grant the SQL Server account access to the MDB on your machine.
> (the above two require proper network security, but should not be difficul
t)
> You can drop the MDB database entirely and move the tables to SQL Server,
> which is probably the best bet. If you absolutely need to access these
> tables via MS Access, you can create linked tables pointing to SQL Server.
> This will put all the tables local in SQL Server, but still let you use yo
ur
> access front end.
> Is there really a need to have SQL server access your local MDB, rather th
an
> migrating the tables and data to SQL Server?
>
> "tech77" <tech77@.discussions.microsoft.com> wrote in message
> news:7B9F4484-F46C-493F-8830-A5602EC96B55@.microsoft.com...
> access to
> use
>
>