MS Access/SQL concurrency Question

  • Thread starter Thread starter mcnews
  • Start date Start date
M

mcnews

if johnny is editing a record and suzie is printing a report that
included the record that johnny is editing will bobby, the boss, see
that record on suzie's report?
how/where can i prove this?

thanks much,
mcnewsxp
 
mcnews said:
if johnny is editing a record and suzie is printing a report that
included the record that johnny is editing will bobby, the boss, see
that record on suzie's report?
how/where can i prove this?

thanks much,
mcnewsxp
Click to expand...

If johnny has not initiated a save yet then the report would contain the
record as it was before the editing began. If it was an insert then it
would not be included in the report.

It's not clear if your subject line is indicating a SQL Server back end or
that you just decided to include "SQL" for some reason. If this is a server
back end then it would depend on the isolation level being used. In some
cases Suzy would block Johnny or vise-versa until their statement was
completed.
 
If johnny has not initiated a save yet then the report would contain the
record as it was before the editing began. If it was an insert then it
would not be included in the report.

It's not clear if your subject line is indicating a SQL Server back end or
that you just decided to include "SQL" for some reason. If this is a server
back end then it would depend on the isolation level being used. In some
cases Suzy would block Johnny or vise-versa until their statement was
completed.

--
Click to expand...
right.
i just about to include that this is a MS Access MDB with tables
linked to a SQL Server backend.
so how do do johnny and suzie control the isolation level being used
on the backend via linked MS Access fornt-end?
 
mcnews said:
right.
i just about to include that this is a MS Access MDB with tables
linked to a SQL Server backend.
so how do do johnny and suzie control the isolation level being used
on the backend via linked MS Access fornt-end?
Click to expand...

With linked tables you don't really have much control other than the locking
property of the form used for edits. To control anything further you would
have to use passthrough queries and/or stored procedures to do everything.

Honestly, this is almost never an issue. Are you having specific problems
now?
 
With linked tables you don't really have much control other than the locking
property of the form used for edits. To control anything further you would
have to use passthrough queries and/or stored procedures to do everything.

Honestly, this is almost never an issue. Are you having specific problems
now?
Click to expand...

naw - just a new Project manager who has no experience using MS
Access. i think he just wants to assert himself and stir up things.
i know first hand that it is never an issue where i work because in
most cases the people/person who uses the MS Access apps that i design
does the data maintenance and reporting. still - when people have
something in their heads it's hard to shake it out sometimes.
your answer is *exactly* what i explained to this guy. hopefully
he'll catch on.
 
Back
Top