A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Record Level Locking



 
 
Thread Tools Display Modes
  #1  
Old October 21st, 2004, 09:10 PM
Sirocco
external usenet poster
 
Posts: n/a
Default Record Level Locking

We have an Access 97 backend, Access 2003 front end. Under
tools/options/advanced is a check box for "Open database using
RecordLevelLocking". I read that the Access 97 backend doesn't support
this, so it should be unchecked. On our front-end's this box is checked,
and I'm not aware of any related problems, so does it matter? Also, is it
sufficient to check (or uncheck) the box on the front end, or should it be
checked (or unchecked) on the back end?

Many thanks in advance.


  #2  
Old October 22nd, 2004, 07:24 AM
Allen Browne
external usenet poster
 
Posts: n/a
Default

Uncheck the box on the front end. The A97 back end does not have this option
(unless you are "opening" it with a later version which is not ideal).

I've never seen anyone else report the issue, but we did strike a flaw where
a DAO transaction would not complete if this box was checked. The code was
designed to merge 2 clients into one, and involved executing quite a string
of action queries to reassign all the related records in many tables from
the client to be deleted to the client to be retained, before finally
removing the client. Once the box was unchecked on the A2000 and A2002
workstations that were linking to the A97 back end, the transaction
completed successfully.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Sirocco" wrote in message
...
We have an Access 97 backend, Access 2003 front end. Under
tools/options/advanced is a check box for "Open database using
RecordLevelLocking". I read that the Access 97 backend doesn't support
this, so it should be unchecked. On our front-end's this box is checked,
and I'm not aware of any related problems, so does it matter? Also, is
it
sufficient to check (or uncheck) the box on the front end, or should it be
checked (or unchecked) on the back end?

Many thanks in advance.



  #3  
Old October 22nd, 2004, 11:01 PM
Sirocco
external usenet poster
 
Posts: n/a
Default

That said, is there any reason to keep the Access 97 backend as is and not
convert it to some newer version? For example, if all the front end's are
Access 2003, should the back end be Access 2003 also, or should we keep it
Access 97 in case down the road someone who's using, say, Access 2000 needs
to access it?

Thanks in advance


"Allen Browne" wrote in message
...
Uncheck the box on the front end. The A97 back end does not have this

option
(unless you are "opening" it with a later version which is not ideal).

I've never seen anyone else report the issue, but we did strike a flaw

where
a DAO transaction would not complete if this box was checked. The code was
designed to merge 2 clients into one, and involved executing quite a

string
of action queries to reassign all the related records in many tables from
the client to be deleted to the client to be retained, before finally
removing the client. Once the box was unchecked on the A2000 and A2002
workstations that were linking to the A97 back end, the transaction
completed successfully.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Sirocco" wrote in message
...
We have an Access 97 backend, Access 2003 front end. Under
tools/options/advanced is a check box for "Open database using
RecordLevelLocking". I read that the Access 97 backend doesn't

support
this, so it should be unchecked. On our front-end's this box is

checked,
and I'm not aware of any related problems, so does it matter? Also, is
it
sufficient to check (or uncheck) the box on the front end, or should it

be
checked (or unchecked) on the back end?

Many thanks in advance.





  #4  
Old October 23rd, 2004, 12:38 AM
Sirocco
external usenet poster
 
Posts: n/a
Default

You're in Western Australia. Interesting that my question travelled about
as far as it could before being answered. I'm outside Washington, DC.
That is profound. In so many ways.

"Sirocco" wrote in message
...
That said, is there any reason to keep the Access 97 backend as is and not
convert it to some newer version? For example, if all the front end's are
Access 2003, should the back end be Access 2003 also, or should we keep it
Access 97 in case down the road someone who's using, say, Access 2000

needs
to access it?

Thanks in advance


"Allen Browne" wrote in message
...
Uncheck the box on the front end. The A97 back end does not have this

option
(unless you are "opening" it with a later version which is not ideal).

I've never seen anyone else report the issue, but we did strike a flaw

where
a DAO transaction would not complete if this box was checked. The code

was
designed to merge 2 clients into one, and involved executing quite a

string
of action queries to reassign all the related records in many tables

from
the client to be deleted to the client to be retained, before finally
removing the client. Once the box was unchecked on the A2000 and A2002
workstations that were linking to the A97 back end, the transaction
completed successfully.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Sirocco" wrote in message
...
We have an Access 97 backend, Access 2003 front end. Under
tools/options/advanced is a check box for "Open database using
RecordLevelLocking". I read that the Access 97 backend doesn't

support
this, so it should be unchecked. On our front-end's this box is

checked,
and I'm not aware of any related problems, so does it matter? Also,

is
it
sufficient to check (or uncheck) the box on the front end, or should

it
be
checked (or unchecked) on the back end?

Many thanks in advance.







  #5  
Old October 23rd, 2004, 04:30 AM
Allen Browne
external usenet poster
 
Posts: n/a
Default

If all the front ends have moved to A2000 or later, DO convert the back end
to at least A2000 format.

A2000 and later use JET 4. To access an A97 back end, the data calls have to
be converted from JET 4 to JET 3.5. While Access does that very, very well,
there is a performance loss in every data fetch and write because the
conversion takes time.

The particular database I referred to (where the transaction failed because
of record-level locking) now has its backend converted to A2000, and the
users reported a perceptible performance gain after the conversion.

For general suggestions on the issues in converting from A97 to later
versions, see:
Converting from Access 97 to 2000, 2002 or 2003
at:
http://members.iinet.net.au/~allenbrowne/ser-48.html

Yes, the planet is an amazingly small village now. :-)

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Sirocco" wrote in message
...
You're in Western Australia. Interesting that my question travelled about
as far as it could before being answered. I'm outside Washington, DC.
That is profound. In so many ways.

"Sirocco" wrote in message
...
That said, is there any reason to keep the Access 97 backend as is and
not
convert it to some newer version? For example, if all the front end's
are
Access 2003, should the back end be Access 2003 also, or should we keep
it
Access 97 in case down the road someone who's using, say, Access 2000

needs
to access it?

Thanks in advance


"Allen Browne" wrote in message
...
Uncheck the box on the front end. The A97 back end does not have this

option
(unless you are "opening" it with a later version which is not ideal).

I've never seen anyone else report the issue, but we did strike a flaw

where
a DAO transaction would not complete if this box was checked. The code

was
designed to merge 2 clients into one, and involved executing quite a

string
of action queries to reassign all the related records in many tables

from
the client to be deleted to the client to be retained, before finally
removing the client. Once the box was unchecked on the A2000 and A2002
workstations that were linking to the A97 back end, the transaction
completed successfully.


"Sirocco" wrote in message
...
We have an Access 97 backend, Access 2003 front end. Under
tools/options/advanced is a check box for "Open database using
RecordLevelLocking". I read that the Access 97 backend doesn't

support
this, so it should be unchecked. On our front-end's this box is

checked,
and I'm not aware of any related problems, so does it matter? Also,

is
it
sufficient to check (or uncheck) the box on the front end, or should

it
be
checked (or unchecked) on the back end?

Many thanks in advance.



 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Change and Save a Record sara Using Forms 0 July 17th, 2004 04:47 PM
How can I move the focus to a control on a subform? Brandon General Discussion 7 July 17th, 2004 01:39 AM
Last record first Alex Using Forms 3 July 12th, 2004 07:21 PM
How to get Current Record from the subform with the datasheet Tom Using Forms 1 June 18th, 2004 12:35 PM
Avoid Creating A Duplicate Record Mark New Users 4 May 11th, 2004 01:52 AM


All times are GMT +1. The time now is 02:45 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.