ACCESS 2007 MSysObjects table

M

MikeL

We have a very large database with 1734 objects. We have been experiencing
numerous performance issues, lockups, repairs sinve converting up to ACCESS
2007. ie. going from design view and back can max out a dual core processor
on both CPUs for 5 minutes. Is there anything we can do short of splitting
this database apart? We have about 100 other MS Databases that are smaller
and are 'mostly' working fine in ACCESS 2007.
 
M

MikeL

I have been testing SP1 on my computer and it does not seem to matter. It
does get worse the longer it is open which may suggest a memory leak, but not
sure how to detect that anyway.
 
C

Clint

I recommend you contact support and have them open a case. I can't really
help you unless we get a repro inhouse and support is the best way to make
that happen. Start at support.microsoft.com.

Clint
 
P

Port 119

Split the database as there are numerous upsides to this!

I use a simple script to allows re-link if the databases are moved to
anotehr folder.

Regards,
Tom Bizannes
Sydney, Australia
 
M

MikeL

Thanks for the advise. The replication in test will not work due to the
number of Table links, etc. that would need to be setup by support.
 
M

MikeL

Eventually we will do a database table split and maybe even a functional
split. I will keep all who replied here posted on what the resolution turns
out to be.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Tiff format problems with Access 2007 1
Moving to Access 2007 from Access 2003 5
Access 2003 On Open Event Error when 2007 installed 8
Access as a Service 8
Shared Access database slow with Access 2007/Vista client. 1
Repair Corrupt Access Database 4
Slow access to Links 5
Vista, Access 2007, SQL Server 2005, Native Client, ODBC: slow for 1

Top