Access Front - SQL Back

Access Front - SQL Back - File Locking

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

BillD - 23 Jan 2008 01:11 GMT

I am experimenting with an Access Front End and an SQL Server Back End with
Linked Tables. I set up SQL Server 2005 Express on my desktop PC and used
SSMA to transfer the tables and some queries to SQL Server. The tables are
linked to the Access 2000 Front End. Everything was working fine but when I
close the Access .mdb Front End file, I sometimes cannot reopen the Access
File. The Access Lock File.9.ldb stays open and does not close when I have
closed the Access File. I am unable to reopen the Access .mdb file. I cannot
delete the .mdb file or the .ldb file. I get a message that I "Cannot delete"
"There has been a sharing violation. Source or destination file may be in
use." I can reboot the computer and then reopen the file and it will then
close correctly.
Does anyone know what I can do to correct this problem?

Bill D

Reply to this Message

BillD - 24 Jan 2008 23:05 GMT

I have posted this Question on the SQL Server forum.

Thanks,
Bill D

> I am experimenting with an Access Front End and an SQL Server Back End with
> Linked Tables. I set up SQL Server 2005 Express on my desktop PC and used
[quoted text clipped - 10 lines]
>
> Bill D

Reply to this Message

BillD - 24 Jan 2008 23:05 GMT

I have posted this question on the Server Forum.

Thanks,
Bill D

> I am experimenting with an Access Front End and an SQL Server Back End with
> Linked Tables. I set up SQL Server 2005 Express on my desktop PC and used
[quoted text clipped - 10 lines]
>
> Bill D

Reply to this Message

Tony Toews [MVP] - 28 Jan 2008 06:02 GMT

>I am experimenting with an Access Front End and an SQL Server Back End with
>Linked Tables. I set up SQL Server 2005 Express on my desktop PC and used
[quoted text clipped - 7 lines]
>use." I can reboot the computer and then reopen the file and it will then
>close correctly.

Check if msaccess.exe is running in the Task Mgr. Ctrl+Alt+Del then
Task Manager. If so try ending the process and see if that solves
your problem.

If so I'd check Access minimizes to Windows 95/NT toolbar instead of
closing
http://www.mvps.org/access/bugs/bugs0005.htm

Tony

Signature

Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Reply to this Message

BillD - 28 Jan 2008 13:37 GMT

Tony:
Thanks for the answer and the Link. A sub form on a main form was causing
the problem.

> >I am experimenting with an Access Front End and an SQL Server Back End with
> >Linked Tables. I set up SQL Server 2005 Express on my desktop PC and used
[quoted text clipped - 17 lines]
>
> Tony

Reply to this Message

Tony Toews [MVP] - 30 Jan 2008 06:21 GMT

>Thanks for the answer and the Link. A sub form on a main form was causing
>the problem.

Now I'm curious. Specifically how? Was it the recordset or the check
box problem or something else?

Tony

Signature

Reply to this Message

BillD - 30 Jan 2008 15:02 GMT

Hi Tony:
I would have to say that it was a recordset problem. I do not have any check
boxes in the sub-forms on the main form. When I entered info for a new call,
the Call ID was showing. When I went to another record and entered info on a
new call then the Call ID for that call went blank and the database locked.
The only way I could get the database working again was to reboot the
computer.
This problem probably occured when I was preparing the Tables and Queries
for migration to SQL Server. I renamed any tables and Queries that had spaces
in the name and I renamed all table fields that had spaces in the name. As a
result I had to check/change Event Procedures. I don't know if I needed to
rename the Tables and Queries or just the Table Field Names? The other thing
I learned is that if a field name has a name in the Caption then a Query or
Event Procedure refers to the Caption and not the field name. I did not
change the Caption when I changed a field name. I found 2 field names that
had original Caption names which I subsequently deleted.
Hope I have explained this properly. Sorry for the rambling, I am not a
programmer.
Thanks again for your valued help.

Bill D

> >Thanks for the answer and the Link. A sub form on a main form was causing
> >the problem.
[quoted text clipped - 3 lines]
>
> Tony

Reply to this Message