Linked Server error

I have created a linked server (LAB) to an Access 2K DB on my local drive.
From within a DB on the SQL server I started to create a view, and using the
syntax:
SELECT * FROM LAB...tblName tblName_1
It displays all the required data.
When I attempt to save the view though, then I get problems. I receive an
error message:
ODBC error:[Microsoft][ODBC SQL Server Driver][SQL Server]Could not start a
transaction OLE DB provider 'Microsoft.Jet.OLEDB.4.0'.
[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB returned message:
Neither the isolation level nor a strengthening of it is supported.]
[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace[OLE/DB
Provider 'Microsoft.Jet.4.0' ITransactionLoca StartTransaction returned
0x8004d008: ISOLEVEL=1048576].
I then placed the SELECT statement in a SProc, and received the following
error:
Error 7392: Could Not start a transaction for OLE DB provider
'Microsoft.Jet.OLEDB.4.0'.
OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.4.0'
ITransactionLocal::StartTransaction returned 0x8004d008: ISOLEVEL=1048576].
Setting the Isolation level as the first statement in the SProc made no
difference.
Anyone have any idea where I have gone wrong? Either I didn't set the Linked
Server up correctly, or I have missed something very fundamental.
Thanks in advanced for any help with this one,
TonyWhy don't you create Access from inside Access and create SQL Proc from SQL
side?
GX
"Logicalman" <tony9scott45us@.com7cast.net34> wrote in message
news:16C30F75-3662-49DD-BA57-28A07A39DC19@.microsoft.com...
>I have created a linked server (LAB) to an Access 2K DB on my local drive.
> From within a DB on the SQL server I started to create a view, and using
> the
> syntax:
> SELECT * FROM LAB...tblName tblName_1
> It displays all the required data.
> When I attempt to save the view though, then I get problems. I receive an
> error message:
> ODBC error:[Microsoft][ODBC SQL Server Driver][SQL Server]Could not start
> a
> transaction OLE DB provider 'Microsoft.Jet.OLEDB.4.0'.
> [Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB returned message:
> Neither the isolation level nor a strengthening of it is supported.]
> [Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace[OLE/DB
> Provider 'Microsoft.Jet.4.0' ITransactionLoca StartTransaction returned
> 0x8004d008: ISOLEVEL=1048576].
> I then placed the SELECT statement in a SProc, and received the following
> error:
> Error 7392: Could Not start a transaction for OLE DB provider
> 'Microsoft.Jet.OLEDB.4.0'.
> OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.4.0'
> ITransactionLocal::StartTransaction returned 0x8004d008:
> ISOLEVEL=1048576].
> Setting the Isolation level as the first statement in the SProc made no
> difference.
> Anyone have any idea where I have gone wrong? Either I didn't set the
> Linked
> Server up correctly, or I have missed something very fundamental.
> Thanks in advanced for any help with this one,
> Tony|||The access DB is a replicant, and, unfortunately, has some data errors in it
.
I originally started importing the data into SQL to complete some web work,
but due to the errors, felt thaat 'linked' tables would suffice for my needs
,
thus, a linked server method raised up and so I tried this. Once the errors
started it then intrigued me to find out why, and thus, I wrote the question
.
".Net Guy" wrote:

> Why don't you create Access from inside Access and create SQL Proc from SQ
L
> side?
> GX
>
> "Logicalman" <tony9scott45us@.com7cast.net34> wrote in message
> news:16C30F75-3662-49DD-BA57-28A07A39DC19@.microsoft.com...
>
>