K
kayesm
Backgroun info:
14 HP nc6320 notebooks
Windows XP-Pro SP2
MS Office 2003 (SP3)
Credential Manager & Fingerprint Software v2.50 Rev.H
ProtectTools Security Manager v3.00 Rev. A
Here's my situation, I have an Access 2003 database on a network server that
each of
these laptops accesses. Each user has a shortcut to the front-end which
asks them
to login and select one of two functions. After choosing a function
(Main/Reports)
it intializes background processes over the network to the backend database.
In the
bottom left hand corner of the Access window is the status bar which says
"Calculizing" and then it says "Form View." Normally this process takes all
of
about 5 seconds from when it says "Calculizing" to "Form View." When they are
finished using their forms, they close down Access and there are no problems.
Last week I installed the latest versions of Credential Manager and
ProtectTools.
Now when my users are logged into CM and they open the Access DB, the status
bar
will say it is "Calculizing..." for upwards of 45 seconds before going to
the "Form
View" staus. The functionality and integrity of the databse appear to be
normal,
but when they are finished and close Access the Windows Task Manager still
shows
"MSACCESS.exe" active in the Processes tab. We cannot reopen the database
unless we
manually shutdown the process.
What i have noticed is if I log them out of CM before opening the Access DB,
it only
takes 5 secs to Calculate and it closes normally without leaving a ghost
process.
If i leave them logged into CM it takes 45 seconds and leaves a ghost
process.
I cannot ask them to log out of CM everytime they want to access the DB
because of
their fingerprint scanning functions, but i also cannot have them having to
wait so
long to initialize the forms and being forced to manually shutdown the
MSACCESS.exe
process.
I have tried everything and i have come up with no viable solutions. Can
anyone
please help me. There has to be some kind of background security when CM is
logged
in that is prohibiting/slowing down Access and is not allowing the process
to close.
14 HP nc6320 notebooks
Windows XP-Pro SP2
MS Office 2003 (SP3)
Credential Manager & Fingerprint Software v2.50 Rev.H
ProtectTools Security Manager v3.00 Rev. A
Here's my situation, I have an Access 2003 database on a network server that
each of
these laptops accesses. Each user has a shortcut to the front-end which
asks them
to login and select one of two functions. After choosing a function
(Main/Reports)
it intializes background processes over the network to the backend database.
In the
bottom left hand corner of the Access window is the status bar which says
"Calculizing" and then it says "Form View." Normally this process takes all
of
about 5 seconds from when it says "Calculizing" to "Form View." When they are
finished using their forms, they close down Access and there are no problems.
Last week I installed the latest versions of Credential Manager and
ProtectTools.
Now when my users are logged into CM and they open the Access DB, the status
bar
will say it is "Calculizing..." for upwards of 45 seconds before going to
the "Form
View" staus. The functionality and integrity of the databse appear to be
normal,
but when they are finished and close Access the Windows Task Manager still
shows
"MSACCESS.exe" active in the Processes tab. We cannot reopen the database
unless we
manually shutdown the process.
What i have noticed is if I log them out of CM before opening the Access DB,
it only
takes 5 secs to Calculate and it closes normally without leaving a ghost
process.
If i leave them logged into CM it takes 45 seconds and leaves a ghost
process.
I cannot ask them to log out of CM everytime they want to access the DB
because of
their fingerprint scanning functions, but i also cannot have them having to
wait so
long to initialize the forms and being forced to manually shutdown the
MSACCESS.exe
process.
I have tried everything and i have come up with no viable solutions. Can
anyone
please help me. There has to be some kind of background security when CM is
logged
in that is prohibiting/slowing down Access and is not allowing the process
to close.