Exclusive Access Conflict

[Guest]

Hey folks!

I got a head-scratcher here (at least for me ... perhaps not for you).

My frontend points to a SQL server database which I have a table of users.
When they first open the app, requires them to log in by selecting a username
from a listbox and entering their password.

Here's the head-scratcher ...

After it appears to populate the listbox, my users get a message box (31
times, everytime) with the following message:
"You do not have exclusive access to the database at this time. If you
proceed to make changes, you may not be able to save them later."

The listbox is populated by a query statement in the Rowsource property on
the Data tab rather than by vba code during the form load operation.

The sql for the rowsource property is
----------------------------------------------------------------------------------------------
SELECT tblUsers.user_id, tblUsers.user_name AS UserName, tblUsers.user_fname
AS [First Name], tblUsers.user_lname AS [Last Name], tblUsers.user_pwd,
tblUsers.user_role
FROM tblUsers
ORDER BY tblUsers.user_lname, tblUsers.user_fname

 

[Douglas J. Steele]

What happens if you copy that SQL statement into a query and run it?

 

[Guest]

I get exactly what I've told it to return to me.

Not so sure it's a SQL issue but, rather, seems more of an environmental
issue.
--
~ Bob Bonta ~

What happens if you copy that SQL statement into a query and run it?

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)

Hey folks!

I got a head-scratcher here (at least for me ... perhaps not for you).

My frontend points to a SQL server database which I have a table of users.
When they first open the app, requires them to log in by selecting a
username
from a listbox and entering their password.

Here's the head-scratcher ...

After it appears to populate the listbox, my users get a message box (31
times, everytime) with the following message:
"You do not have exclusive access to the database at this time. If you
proceed to make changes, you may not be able to save them later."

The listbox is populated by a query statement in the Rowsource property on
the Data tab rather than by vba code during the form load operation.

The sql for the rowsource property is:
----------------------------------------------------------------------------------------------
SELECT tblUsers.user_id, tblUsers.user_name AS UserName,
tblUsers.user_fname
AS [First Name], tblUsers.user_lname AS [Last Name], tblUsers.user_pwd,
tblUsers.user_role
FROM tblUsers
ORDER BY tblUsers.user_lname, tblUsers.user_fname;

 

['69 Camaro]

Hi, Bob.

After it appears to populate the listbox, my users get a message box (31
times, everytime) with the following message:
"You do not have exclusive access to the database at this time. If you
proceed to make changes, you may not be able to save them later."

If they have Adobe Acrobat Writer 7.0 installed, then it's the PDFMaker
Add-in causing the problem, because it needs exclusive access to the
database file to add the Adobe CommandBar. If they're not squeamish about
making changes to the Windows Registry, have them change the value of this
key:

HKEY_LOCAL_MASCHINE\Software\Microsoft\Office\ACCESS\Addins\PDFMaker.Office­Addin
LoadBehavior

from 3 to 0

Otherwise, run the Adobe Acrobat installation again in modify mode and
deselect the PDFMaker for Access only (so it remains for the other installed
MS Office applications), and they'll get rid of the Adobe CommandBar items
for all of their versions of Access on that computer, yet still keep it for
all of the other MS Office applications.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

Hey folks!

I got a head-scratcher here (at least for me ... perhaps not for you).

My frontend points to a SQL server database which I have a table of users.
When they first open the app, requires them to log in by selecting a
username
from a listbox and entering their password.

Here's the head-scratcher ...

After it appears to populate the listbox, my users get a message box (31
times, everytime) with the following message:
"You do not have exclusive access to the database at this time. If you
proceed to make changes, you may not be able to save them later."

The listbox is populated by a query statement in the Rowsource property on
the Data tab rather than by vba code during the form load operation.

The sql for the rowsource property is:
----------------------------------------------------------------------------------------------
SELECT tblUsers.user_id, tblUsers.user_name AS UserName,
tblUsers.user_fname
AS [First Name], tblUsers.user_lname AS [Last Name], tblUsers.user_pwd,
tblUsers.user_role
FROM tblUsers
ORDER BY tblUsers.user_lname, tblUsers.user_fname;

 

[Guest]

Hey Gunny!

Sorry for the long delay to your reply ... I was out of town on a last
minute family related issue.

I'm curious, though, how we got over to discussing Adobe Acrobat Writer 7.0?
I don't think my problem description included anything that would suggest an
issue with AAW7 ... it's a simple sql command to populate a listbox on a form.

If I've missed something, I apologize ... but how does the problem statement
relate to AAW7.0?

w/r,

~ Bob Bonta ~

Hi, Bob.

After it appears to populate the listbox, my users get a message box (31
times, everytime) with the following message:
"You do not have exclusive access to the database at this time. If you
proceed to make changes, you may not be able to save them later."

If they have Adobe Acrobat Writer 7.0 installed, then it's the PDFMaker
Add-in causing the problem, because it needs exclusive access to the
database file to add the Adobe CommandBar. If they're not squeamish about
making changes to the Windows Registry, have them change the value of this
key:

HKEY_LOCAL_MASCHINE\Software\Microsoft\Office\ACCESS\Addins\PDFMaker.Office­Addin
LoadBehavior

from 3 to 0

Otherwise, run the Adobe Acrobat installation again in modify mode and
deselect the PDFMaker for Access only (so it remains for the other installed
MS Office applications), and they'll get rid of the Adobe CommandBar items
for all of their versions of Access on that computer, yet still keep it for
all of the other MS Office applications.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

Hey folks!

I got a head-scratcher here (at least for me ... perhaps not for you).

My frontend points to a SQL server database which I have a table of users.
When they first open the app, requires them to log in by selecting a
username
from a listbox and entering their password.

Here's the head-scratcher ...

After it appears to populate the listbox, my users get a message box (31
times, everytime) with the following message:
"You do not have exclusive access to the database at this time. If you
proceed to make changes, you may not be able to save them later."

The listbox is populated by a query statement in the Rowsource property on
the Data tab rather than by vba code during the form load operation.

The sql for the rowsource property is:
----------------------------------------------------------------------------------------------
SELECT tblUsers.user_id, tblUsers.user_name AS UserName,
tblUsers.user_fname
AS [First Name], tblUsers.user_lname AS [Last Name], tblUsers.user_pwd,
tblUsers.user_role
FROM tblUsers
ORDER BY tblUsers.user_lname, tblUsers.user_fname;

 

[Douglas J. Steele]

Adobe Acrobat Writer is known to install something that interferes with
Access.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

Hey Gunny!

Sorry for the long delay to your reply ... I was out of town on a last
minute family related issue.

I'm curious, though, how we got over to discussing Adobe Acrobat Writer
7.0?
I don't think my problem description included anything that would suggest
an
issue with AAW7 ... it's a simple sql command to populate a listbox on a
form.

If I've missed something, I apologize ... but how does the problem
statement
relate to AAW7.0?

w/r,

~ Bob Bonta ~

Hi, Bob.

After it appears to populate the listbox, my users get a message box
(31
times, everytime) with the following message:
"You do not have exclusive access to the database at this time. If you
proceed to make changes, you may not be able to save them later."

If they have Adobe Acrobat Writer 7.0 installed, then it's the PDFMaker
Add-in causing the problem, because it needs exclusive access to the
database file to add the Adobe CommandBar. If they're not squeamish
about
making changes to the Windows Registry, have them change the value of
this
key:

HKEY_LOCAL_MASCHINE\Software\Microsoft\Office\ACCESS\Addins\PDFMaker.Office­Addin
LoadBehavior

from 3 to 0

Otherwise, run the Adobe Acrobat installation again in modify mode and
deselect the PDFMaker for Access only (so it remains for the other
installed
MS Office applications), and they'll get rid of the Adobe CommandBar
items
for all of their versions of Access on that computer, yet still keep it
for
all of the other MS Office applications.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

Hey folks!

I got a head-scratcher here (at least for me ... perhaps not for you).

My frontend points to a SQL server database which I have a table of
users.
When they first open the app, requires them to log in by selecting a
username
from a listbox and entering their password.

Here's the head-scratcher ...

After it appears to populate the listbox, my users get a message box
(31
times, everytime) with the following message:
"You do not have exclusive access to the database at this time. If you
proceed to make changes, you may not be able to save them later."

The listbox is populated by a query statement in the Rowsource property
on
the Data tab rather than by vba code during the form load operation.

The sql for the rowsource property is:
----------------------------------------------------------------------------------------------
SELECT tblUsers.user_id, tblUsers.user_name AS UserName,
tblUsers.user_fname
AS [First Name], tblUsers.user_lname AS [Last Name], tblUsers.user_pwd,
tblUsers.user_role
FROM tblUsers
ORDER BY tblUsers.user_lname, tblUsers.user_fname;