problem opening tables

[SusanJ]

It's taking a REALLY long time up open VERY small tables & I'm worried. Is
this a sign of a corrupt database? I did compact & repair & it didn't help.
Any ideas?

Thanks

 

[pietlinden]

It's taking a REALLY long time up open VERY small tables & I'm worried.  Is
this a sign of a corrupt database?  I did compact & repair & it didn't help.  
Any ideas?

Thanks

Are they local tables? Are the proper fields indexed? More
information please... Can't answer from the information provided...

You could try making a copy of your database and doing a compact/
repair and see if that helps... is this across a network?

 

[a a r o n . k e m p f]

yes-- it's obvious to me that you've put your data in the wrong
database format

you should upsize to SQL Server--- no matter what-- or find someone
that can

 

[Aaron Kempf knows nothing]

yes-- it's obvious to me that no matter what find someone
that can

 

[Aaron Kempf knows nothing]

I suck and know nothing about Access - I should be quiet and go away

 

[Tony Toews [MVP]]

It's taking a REALLY long time up open VERY small tables & I'm worried. Is
this a sign of a corrupt database? I did compact & repair & it didn't help.
Any ideas?

The three most common performance problems in Access 2000 or newer
are:
- LDB locking which a persistent recordset connection or an always
open bound form corrects (multiple users)
- sub datasheet Name property set to [Auto] should be [None]
- Track name AutoCorrect should be off

If the problem is for everyone when starting up the MDB then it likely
needs a decompile.

For more information on these, less likely causes, other tips and
links to MS KB articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

Please ignore any postings by Aaron Kempf as he is rather
monomaniacal.

Tony
--
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/

 

[SusanJ]

Thanks everyone for your input. I think my PC was just totally worn out. I
open & close many large Access & Excel files throughout the day. The next
morning, all was well. By the way, this was not on a network, and these were
tables with about 75 records and 10 fields.

It's taking a REALLY long time up open VERY small tables & I'm worried. Is
this a sign of a corrupt database? I did compact & repair & it didn't help.
Any ideas?

The three most common performance problems in Access 2000 or newer
are:
- LDB locking which a persistent recordset connection or an always
open bound form corrects (multiple users)
- sub datasheet Name property set to [Auto] should be [None]
- Track name AutoCorrect should be off

If the problem is for everyone when starting up the MDB then it likely
needs a decompile.

For more information on these, less likely causes, other tips and
links to MS KB articles visit my Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

Please ignore any postings by Aaron Kempf as he is rather
monomaniacal.

Tony
--
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/

 

[So Sorry For Poor Aaron]

"Aaron Kempf knows nothing"

u rite bro

aaron him don kno nuttin

he give them big boys any lip they show him nuttin

they nut him good

then he cry momma momma dey hurts me

he ain gon giv um no lip tho

he likes um lots and lots

he they pussybaby

 

[Tony Toews [MVP]]

Thanks everyone for your input. I think my PC was just totally worn out. I
open & close many large Access & Excel files throughout the day. The next
morning, all was well. By the way, this was not on a network, and these were
tables with about 75 records and 10 fields.

Very interesting. Presumably you rebooted the PC over night. Sounds
like a severe memory leak somewhere.

Tony
--
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/

 

[a a r o n . k e m p f]

JET is one big memory leak.
if you don't explicitly close your variables, and de-instantiate
them-- you'll have memory leaks.. especially if you get code from
these kids.

it's much better to move to ADO and ADP because 'things just work'
then and you can use your code in ASP for example

 

[bcap]

Ignore Kempf, he is an idiot, a liar and a convicted criminal.

 

[a a r o n . k e m p f]

I'm not an idiot, or a racist, nor a convicted criminal

 

[Aaron Kempf knows nothing]

I'm an idiot, a racist, a convicted criminal