Home > Archive > SQL Anywhere database > June 2005 > ODBC Error - "Can Not Lock All Records"









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author ODBC Error - "Can Not Lock All Records"
Paul

2005-06-27, 3:23 am

Hello Everyone:

I am converting Access to SQL Anywhere / ASA. The UI is staying as an
Access MDB, but the Data is SQL Anywhere on a server.
When I go to run a query from the UI (either Pass-Thru query or a straight
Access query) on the server there's no problem.

When I try to run the query from a client machine reading data from the
server, I get an error message "run-time error '3254; ODBC - Can Not Lock
All Records".

Has anyone gotten this error before and resolved it? If so, how?

Thank you very much in advance for your help.

Sincerely,
Paul Grossman
PAULGRO Consulting LLC


Paul

2005-06-27, 1:23 pm

Hello everyone:

I found the solution at the following newsgroup posting:
http://groups-beta.google.com/group...70c3a
ef2


I was able to resolve it by going to Tools-->Options, Advanced tab. Under
"Default
record locking" "All records" was selected. I then selected "No locks" and
that fixed the problem

Thanks for reading and for your help again.

Sincerely,
Paul Grossman
PAULGRO Consulting LLC


"Paul" <paul.grossman@paulgro.com> wrote in message
news:42bfac16$1@foru
ms-1-dub...
> Hello Everyone:
>
> I am converting Access to SQL Anywhere / ASA. The UI is staying as an
> Access MDB, but the Data is SQL Anywhere on a server.
> When I go to run a query from the UI (either Pass-Thru query or a straight
> Access query) on the server there's no problem.
>
> When I try to run the query from a client machine reading data from the
> server, I get an error message "run-time error '3254; ODBC - Can Not Lock
> All Records".
>
> Has anyone gotten this error before and resolved it? If so, how?
>
> Thank you very much in advance for your help.
>
> Sincerely,
> Paul Grossman
> PAULGRO Consulting LLC
>



Greg Fenton

2005-06-27, 1:23 pm

Paul wrote:
>
> I found the solution at the following newsgroup posting:
> http://groups-beta.google.com/group...70c3a
ef2

>
> I was able to resolve it by going to Tools-->Options, Advanced tab. Under
> "Default record locking" "All records" was selected. I then selected "No locks" and
> that fixed the problem
>


Paul,

Thank you for posting back and providing your solution! Hopefully it
will be helpful for others down the road.

greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
Uwe Sauerbrey

2005-06-30, 7:24 am

Hi Paul,

some time ago I was working with a similar configuration but with MS
SQL-Server as backend.

I learned that Access has problems to identify rows for deletes and updates
when:
1. The table to be updated has no primay key.
2. The primary key includes a column with a datatype that Access does not
know.

Greetings
Uwe

"Paul" <paul.grossman@paulgro.com> schrieb im Newsbeitrag
news:42bfac16$1@foru
ms-1-dub...
> Hello Everyone:
>
> I am converting Access to SQL Anywhere / ASA. The UI is staying as an
> Access MDB, but the Data is SQL Anywhere on a server.
> When I go to run a query from the UI (either Pass-Thru query or a straight
> Access query) on the server there's no problem.
>
> When I try to run the query from a client machine reading data from the
> server, I get an error message "run-time error '3254; ODBC - Can Not Lock
> All Records".
>
> Has anyone gotten this error before and resolved it? If so, how?
>
> Thank you very much in advance for your help.
>
> Sincerely,
> Paul Grossman
> PAULGRO Consulting LLC
>
>



Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com