Hi.
I know the question is kind of vague.
But I was out the week of Christmas, and then I get an email saying Access for users isn't opening any tables, queries, or forms.
Hi.
I know the question is kind of vague.
But I was out the week of Christmas, and then I get an email saying Access for users isn't opening any tables, queries, or forms.
Yes, very vague.
Any messages?
Please use # icon on toolbar when posting code snippets.
Cross Posting: https://www.excelguru.ca/content.php?184
Debugging Access: https://www.youtube.com/results?sear...bug+access+vba
You sure thats the right database file? In File Explorer what is the size? Do you have a backup? Is that a backend database or the frontend?
Yes, I believe so. This has been the Access file for years now. This happened right before new years.
It is 412kB. Should be much larger.
I do, but the backups are different sizes as well. I just tried opening the backup, it is saying "'Id' is not a index in this table."
Backend db.
Hi
Can you upload the Database to see if anyone else can view the tables?
You can PM me if you need further help.
Good Reading https://docs.microsoft.com/en-gb/off...on-description
So answer the basics
Is your db split?
If it is, is the front end shared?
How many users?
is this happening to every user or just some?
does it happen on other databases, or just this one?
implies your db is corrupted. So you need to find a valid backupI just tried opening the backup, it is saying "'Id' is not a index in this table."
Go into the design of the front end, see if tables there and can you click and open them and do they have data. I assume the backend is an Access db?
The DB might be, how do I find out?
30 users.
Every user that uses this Db.
Nope, just this one.
Where else can a valid backup be stored?
I am be able to load all tables and data on Microsoft SQL Server side of things. This is the root and parent Db. Restricted mainly to the DBA.
This Access Db was created for business users. So they can view data easily.
If the FE is not showing any tables try Relinking to the BE
You can PM me if you need further help.
Good Reading https://docs.microsoft.com/en-gb/off...on-description
Okay, I was able to locate a working back up.
Easy fix on my end.
Thanks all.
you said the BE is sql server, so it is splitThe DB might be, how do I find out?
doesn't answer the question. Does every user have a copy of the FE (the Access bit) on their own machine? Or is it located in a shared location and every user uses it?Every user that uses this Db.
From what you have said, it sounds like the latter. If they are using a shared copy, you will suffer from corruption and this will happen again. Fortunately you have a separate BE which provides some protection for your data.
The setup should be every user has a copy of the FE (the Access bit) on their own machine. And the connection to sql server should be over wire, not wifi.
That is up to you. The working copy you found - make sure you put a copy somewhere safe where it a) cannot be interfered with and b) cannot be deleted. It may be if this is a backup, the seeds of corruption have already have been sown, it's just not apparent yet. So I would create a new access file and import all the objects. Then compact repairWhere else can a valid backup be stored?
Got it, thanks.you said the BE is sql server, so it is split
It is in a shared location. What is happening is that we are creating a shortcut to their desktop to the Access bit.doesn't answer the question. Does every user have a copy of the FE (the Access bit) on their own machine? Or is it located in a shared location and every user uses it?
Silly question, how do I go about setting this up?The setup should be every user has a copy of the FE (the Access bit) on their own machine. And the connection to sql server should be over wire, not wifi.
And they are wired.
I will make backups of the working backup. I will clean up all the network paths for this Access bit.That is up to you. The working copy you found - make sure you put a copy somewhere safe where it a) cannot be interfered with and b) cannot be deleted. It may be if this is a backup, the seeds of corruption have already have been sown, it's just not apparent yet. So I would create a new access file and import all the objects. Then compact repair
I will create a new access file, import all objects, and then compact repair.
Thanks for the feedback. Appreciate it.