'Could not find the object' error

[Mohamster]

Hi everyone,

The Problem: When I try and open one of my tables tblSiteInfo in datasheet view I receive the following error:
​

'The Microsoft Access Database engine could not find the object ". Make sure the object exists and that you spell its name and the path name correctly'

This only happens when I open it in datasheet view, if I open the table in design view all is fine. The error message displays twice before allowing me to proceed to the table.

The table has no lookup fields in it and consists mainly of number and text fields in addition to one attachment field.
​

I've looked around and this seems to be a common error. Having tried a few of the suggested solutions in previous threads to no avail I'm stumped. I checked the table and all other tables in the database for lookup fields referring to or referred by tblSiteInfo.

I've recently been adding a lot of new tables and establishing relationships between them in the 'Relationships' window. I've also been renaming a few of my tables to eliminate spaces and wonder if this is somehow causing the problem? Problem is I don't know where exactly to look to check whether this renaming is causing the error.

On a wider note, this database started out full of lookup fields within tables and has been totally revamped based on some advice received in this forum (See link to other post). I'm wondering any previous design errors are now biting me in the ass and whether I should bite the bullet and start fresh to avoid future problems.

Any thoughts on the error resolution and on the wider matter.

Many thanks,
Mohammed

 

[GinaWhipp]

When was the last time you Compiled? (Make a back-up first). I would also make sure *Track Autoname* is unchecked and then Compact and Repair your database.

 

[Mohamster]

Thanks Gina. That fixed it. While I was digging around in exasperation today I found the object dependencies tab and tblSiteInfo was dependent upon a randomly named field that didn't seem to exist, it was deleted from the dependencies tab after the compact and repair operation that you suggested.

This problem has made me worry that I may be putting in place/have already put in place bad practices (I am not experienced in MS-Access by any stretch of the imagination, I'm building this database for my work and am learning as I go along!).

Just wondering if I should pause now before I go any deeper and check for any other bad design practices?

I've already ensured that I use no lookup fields in tables, no 'Yes/No' fields either and I'm tending towards a rational naming convention.

Something I've seen suggested is splitting the database. It will eventually be used by myself and a colleague with some thoughts of trying to enable data input through our website (although this is somewhat unlikely!).

Thanks again,
Mohammed

 

[GinaWhipp]

Hmm, here are few things that might help you with best practices...

My Database Standards...
http://regina-whipp.com/blog/?p=102

Setting up a Model Database...
http://www.access-diva.com/d11.html

Information on splitting...
Does everyone have their own front end? Are their front ends installed on their drive and the back-end on a shared drive? Is the database opening in shared mode? Perhaps the below will help…
http://www.kallal.ca/Articles/split/index.htm
http://allenbrowne.com/ser-01.html

You may also want to take a look at MVP Tom Wickerath's article…
http://www.accessmvp.com:80/Twickerath/articles/multiuser.htm

To handle the update of multiple front ends see…
http://www.autofeupdater.com/
http://regina-whipp.com/blog/?p=184
http://www.btabdevelopment.com/ts/freetools

If each user needs Access you can install the Runtime…
Access 2007
http://www.microsoft.com/downloads/...d9-9dc6-4b38-9fa6-2c745a175aed&displaylang=en

Access 2010
http://www.microsoft.com/downloads/...cd-5250-4df6-bfd1-6ced700a6715&displaylang=en

Access 2013
http://www.microsoft.com/en-us/download/details.aspx?id=39358