Getting mdb to work in Access 2000 runtime / Slow in Access 2007

[DIH]

Our company recently rolled out new pcs (DuoCore P4 with 1 GB ram) with
Office 2007 pre-installed. All my databases ran very smoothly when
running in Access 2000 through 2003 on Pentium 2 pcs with 256 MB ram.
Now with 2007, they run VERY slow. Just entering into a new field in a
form (or even directly in a table) causes the cursor to pause anywhere
between 5 and 20 seconds! What happens is the cursor will blink 2 or 3
times and then stop for 5 to 20 seconds - anything typed in while the
cursor is paused will not show up when the cursor starts blinking again.
You can imagine how annoying this is!

We tried running the databases (which by the way are not split and are
on a Novell file server)using Access 2000 runtime (which got installed
with another application called PMC 2000). This solution works perfectly
on my pc.

The problem is that on a number of other pc's on the network, the file
will open in the 2000 runtime but any commands you click will only
result in the following error:

"The expression onClick you entered as the event property setting
produced the following error:
The expression may not result in the name of a macro, the name of a user
defined function, or event procedure.
There may have been an error evaluating the function, event or macro."

Note that I have admin rights to my machine but the users on the problem
machines do not. I don't know if this is an issue or not. These users
have no problem running PMC 2000(which utilizes Access 2000 runtime)on
their machines.

If there is any other info I need to post, please let me know. I'm at my
wits end with this problem (not to mention the frustration from all the
calls I get from the disgruntled users that have to contend with this
issue in Access 2007).

Any solution for either speeding up 2007 or getting the database to run
in the 2000 runtime is greatly appreciated.

TIA

Dave

 

[Arvin Meyer [MVP]]

1. While Access 2000 and 2007 can be run on the same machine, it takes a
very long time to switch between them.

2. If you are running Vista with Office 2007, I'd recommend 2 GB of RAM for
acceptable performance.

3. Unless you want to corrupt your database, split it and run only the data,
back-end on the server.

4. Admin permissions are not necessary, but you need to have adequate
file/directory permissions on both the server and workstation (Everything
but Full Control is what I usually recommend)

 

[DIH]

1. While Access 2000 and 2007 can be run on the same machine, it takes a
very long time to switch between them.

The users on these machine don't really need to use anything but the
couple of databases (basically 98% of the time they are using the
databases, the other 2% email.)So even if it took a while to switch,
they would MUCH prefer that to the horrible performance they are getting
in Access 2007. Please note that I'm not bashing 2007 but the databases
are virtually unusable when running under it.

2. If you are running Vista with Office 2007, I'd recommend 2 GB of RAM for
acceptable performance.

The pcs are running xp pro sp2.

3. Unless you want to corrupt your database, split it and run only the data,
back-end on the server.

I agree, but logistically in my company that would be incredibly
difficult(take my word for it on that one!). I have the databases backed
up in multiple locations. Also note that we have run these databases
without incident for over 18 months.

4. Admin permissions are not necessary, but you need to have adequate
file/directory permissions on both the server and workstation (Everything
but Full Control is what I usually recommend)

I'm not in the IT dept but I'm fairly sure the users have the correct
permissions set. I also think that pmc 2000 (runtime) was installed
first and then Office 2007. Should we reinstall the runtime?
Bottom line, I really would like to get these databases to run in the
2000 runtime.

Thanks again,

Dave

 

[Arvin Meyer [MVP]]

I'm not in the IT dept but I'm fairly sure the users have the correct
permissions set. I also think that pmc 2000 (runtime) was installed first
and then Office 2007. Should we reinstall the runtime?
Bottom line, I really would like to get these databases to run in the 2000
runtime.

If the users are not using anything in Access 2007 except for your
databases. I'd use the Access 2000 runtime. Be aware of several things.

1. You MUST install in a separate directory or you will either fail the
install or overwrite many of your Access 2007 files.

2. If you are still having problems, you may have to uninstall Office 2007,
then install The runtime, then reinstall Office 2007 (with or without
Access)

 

[DIH]

If the users are not using anything in Access 2007 except for your
databases. I'd use the Access 2000 runtime. Be aware of several things.

1. You MUST install in a separate directory or you will either fail the
install or overwrite many of your Access 2007 files.

2. If you are still having problems, you may have to uninstall Office 2007,
then install The runtime, then reinstall Office 2007 (with or without
Access)

Thank you much Arvin. I will relay this info to the IT guys and
hopefully get it to all work out.

Dave