Cant re-open Access mdb file to change design

[Rod]

After changing the design in a Microsoft Access mdb file
used with my FrontPage 2000 web site, Access closes, but
actually continues to have a process running. I have to
end that process before I am able to re-open the Access
mdb file. Also, it is EXTREMEMLY slow to save and close
the Access file and return to Frontpage. I'm sure there's
a simple answer for this, but I haven't been able to find
it. Who can help?

 

[Jim Buyens]

-----Original Message-----

After changing the design in a Microsoft Access mdb file
used with my FrontPage 2000 web site, Access closes, but
actually continues to have a process running. I have to
end that process before I am able to re-open the Access
mdb file. Also, it is EXTREMEMLY slow to save and close
the Access file and return to Frontpage. I'm sure there's
a simple answer for this, but I haven't been able to find
it. Who can help?

When you double-click an .mdb file in an open Web,
FrontPage:

1. Copies the file to your local disk.
2. Starts Access, pointing it to the new local copy
of your database.

Then, each time FrontPage receives the focus, it checks to
see if the time stamp on the temporary copy of your
database has changed. If so, it imports the database.

Obviously, if your PC and the hosted Web site are
connected by a slow link, all this copying to and fro and
importing is going to take a long time.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Guest]

-----Original Message-----

When you double-click an .mdb file in an open Web,
FrontPage:

1. Copies the file to your local disk.
2. Starts Access, pointing it to the new local copy
of your database.

Then, each time FrontPage receives the focus, it checks to
see if the time stamp on the temporary copy of your
database has changed. If so, it imports the database.

Obviously, if your PC and the hosted Web site are
connected by a slow link, all this copying to and fro and
importing is going to take a long time.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

.

I have a DSL (fast) connection, and the MDB file just over
1 mg. It doesn't appear to me that ACCESS is really
closing, and therefore I have to bring up the task list
and delete the MSACCESS.EXE process(s) that are running.
Even outside of FrontPage I get the multiple ms access
processes. Can this be prevented, so that Access really
does stop the process when your close the application
interface.

 

[Jim Buyens]

I have a DSL (fast) connection, and the MDB file just over
1 mg. It doesn't appear to me that ACCESS is really
closing, and therefore I have to bring up the task list
and delete the MSACCESS.EXE process(s) that are running.
Even outside of FrontPage I get the multiple ms access
processes. Can this be prevented, so that Access really
does stop the process when your close the application
interface.

That's pretty weird. Are you up-to-date with all Windows updates,
Office service releases, and MDAC 2.8?

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Guest]

Weird huh? Gee, I've had this problem on every computer
and operating system I've used. I just thought it was a
bug that everyone had to put up with. My Windows Update is
up-to-date. I'm not sure how to check the other two things
you mentioned. It might be less confusing for me to
communicate via EMAIL. Can we do that, or is that not an
option?
Thanks,
Rod

-----Original Message-----

I have a DSL (fast) connection, and the MDB file just over
1 mg. It doesn't appear to me that ACCESS is really
closing, and therefore I have to bring up the task list
and delete the MSACCESS.EXE process(s) that are running.
Even outside of FrontPage I get the multiple ms access
processes. Can this be prevented, so that Access really
does stop the process when your close the application
interface.

That's pretty weird. Are you up-to-date with all Windows updates,
Office service releases, and MDAC 2.8?

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------
.
[/QUOTE]

 

[Jim Buyens]

Weird huh? Gee, I've had this problem on every computer
and operating system I've used. I just thought it was a
bug that everyone had to put up with. My Windows Update is
up-to-date. I'm not sure how to check the other two things
you mentioned.

To check office update for service releases, browse
http://office.microsoft.com/officeupdate
and click Check For Updates.

To check your MDAC (Microsoft Data Access Components) version,
inspect the registry value:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess\FullInstallVer

FWIW, I just started access, opened a database, checked running
processes in Task Manager, and found msaccess.exe. Then, I closed
access and checked Task Manager again. There was no msaccess.exe
running.

Is it possible you were physically opening the same database that
IIS was using? Like, were you opening
c:\inetpub\wwwroot\myweb.fpdb\mydata.mdb or some similar location?
If you, IIS may be the culprit. After an ASP page finishes running
and relinquishes a database connection, IIS holds the connection open
for a while in case another request for the same database
(with the same security) comes along.

It might be less confusing for me to communicate via EMAIL. Can we
do that, or is that not an option?

I try to avoid that, mainly because when I answer questions on-on-one,
other people searching newsgroups for help won't find the conversation.

In any event, this is starting to feel more like an Access question than
a FrontPage question. Have you tried the Access newsgroups?

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------