Another ODBC 5.0 question-resolved

Yahoo Archive
1
Hi all,

going thru the list, I found this message which applies to a situation I'm
having here too.

Setting the Isolation Level to READ UNCOMMITTED in a System DSN effectively
solved the problem.

The difference is that I want to use a File DSN, and it doesn't seem like I
can set the Isolation Level parameter directly from the ODBC manager.

So, is there anyway to edit the File DSN to manually set this parameter, or
do I absolutely have to use a System DSN ?

Best regards,

Luc Morin
Electrical Designer
Wulftec International
lucm@...
(819) 838-4232, ext. 232


-----Original Message-----
From: sarah.vareschi@... [mailto:sarah.vareschi@...]
Sent: Friday, November 09, 2001 9:16 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Another ODBC 5.0 question-resolved


In regards to the error message I posted ysterday: Failure getting
record lock on a record from table [Vantage Table Name] (#-210015).

I submitted this question to Tech support also and got the answer
this moring which i tested and works. So, in case anyone else comes
accross this, the solution is:

Go to the Advanced tab of the ODBC DSN and change the Default
Isolation Level to:"Read Uncommitted" This will allow you to get
records even when the table is locked.
2
Ever since the upgrade to 5.0, when I run access queries and reports, I
occaisonally get the error:

Failure gettign record lock on a record from table [Vantage Table Name]
(#-210015).

When I check the locks, that table is indeed locked, but why does that
prevent an access report from running, I'm not trying to update data.

I never got this on 4.0. Does anybody know if there is some kind of setting
that lets me query records even if they are locked?


[Non-text portions of this message have been removed]
3
Boy, that's a new one Sarah. I've never seen that error in 5.0 at all.

Troy Funte
Liberty Electronics

----- Original Message -----
From: sarah.vareschi@...
To: vantage@yahoogroups.com
Sent: Thursday, November 08, 2001 3:01 PM
Subject: [Vantage] Another ODBC 5.0 question



Ever since the upgrade to 5.0, when I run access queries and reports, I
occaisonally get the error:

Failure gettign record lock on a record from table [Vantage Table Name]
(#-210015).

When I check the locks, that table is indeed locked, but why does that
prevent an access report from running, I'm not trying to update data.

I never got this on 4.0. Does anybody know if there is some kind of setting
that lets me query records even if they are locked?


[Non-text portions of this message have been removed]


Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/links

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



[Non-text portions of this message have been removed]
4
In regards to the error message I posted ysterday: Failure getting
record lock on a record from table [Vantage Table Name] (#-210015).

I submitted this question to Tech support also and got the answer
this moring which i tested and works. So, in case anyone else comes
accross this, the solution is:

Go to the Advanced tab of the ODBC DSN and change the Default
Isolation Level to:"Read Uncommitted" This will allow you to get
records even when the table is locked.