Front End doesn't load if back end is missing

[JamesDeckert]

I'm trying to implement the J Street Relinker on a db which has just been split into FE/BE. I've used the relinker on another db and I don't think the problem is the relinker.
If I rename the BE, then when loading the FE, I get the Access screen as if no db was loaded.

If I select the db on the left of this screen I go to the "New" screen to allow me to create a new db. I'm using Access 2016, but I tried this same thing (renaming the BE) on my other db and the relinker popped up with a browse screen to allow me to choose the BE, which is what I want for the new db.
The new db was originally set up to load the splash page in the Options>Current Database>Display Form. My old db used an AutoExec macro to load the splash page and relinking code so I changed the new db to use an Autoexec macro, which runs fine if the BE is where it should be, but goes to the previous pic if there is no BE. I've put a msgbox as the first line in the Autoexec Macro and it doesn't display if the BE is missing, but pops up fine if the BE is available.
Any ideas on what is going on that my code is not executing if the BE is missing? I just recently inherited this db, so I didn't develop it.


thanks

[ItsMe]

If you rename a file, the files in your Recent Files list will not necessarily be correct.

[JamesDeckert]

I'm renaming the BE, but loading the FE. So that shouldn't have changed. I dbl-clicked FE from the HD just to make sure and the same thing happened.

[ItsMe]

It may be that Access 2016 does not like an Auto Exec or the form that is loading on Start Up. Can you use the Shift Key to Bypass start up stuff? I would make a copy of the FE and place a copy on the machine with A2016's hard drive. Select the file and then use the Shift Key with the Enter key to launch it. Let Access do a JIT and open the file. Do a compact and repair and then try again, without the Shift Key bypass stuff.

[JamesDeckert]

Can you use the Shift Key to Bypass start up stuff?

Yes, if BE missing, gives same pic as above. If BE is available I get a normal blank screen with DB open.

I would make a copy of the FE and place a copy on the machine with A2016's hard drive.

This is being done on a laptop, no network drive involved.

Do a compact and repair and then try again, without the Shift Key bypass stuff.

No difference, Did a decompile/recompile also, no difference.

[ItsMe]

Using Access 2016, I would create a new db and import the objects to the new DB. With the appropriate BE file, I would do a compact and repair on the new front end file.

With that, I would see if the symptom persists. I suspect the code and or the AutoExec are creating issues. But, the way you describe the Shift key thing, this does not seem to be the issue.

[JamesDeckert]

Using Access 2016, I would create a new db and import the objects to the new DB.

Done... No difference.

I deleted the Autoexec macro, so if the BE is available no code runs automatically. Same results. If BE is available db loads but a blank Access screen with tables,etc available in Navigation Pane. If BE missing, I get pic as above.

[ItsMe]

Yeah, seems like 2016 does not like the fact that the linked tables are broken. I wonder if running the link manager in the new FE file you created would give it the appropriate kick. Opening the Link manager might help, but without any broken links, you won't be able to actually run the wizard.

If you open the new FE file with the appropriate BE, you should be able to change the BE file name with the FE still open. Just do not open any tables. In other words, if you are not looking at the data in the BE, there will not be a lock file created and you should be able to move and or rename the BE file.

With the BE file renamed, you should be able to launch and run the Link Manager.

[JamesDeckert]

Did what you suggested, loaded new FE, renamed BE, relinked, reloaded. New FE loaded fine. Closed FE. But as soon as I renamed the BE and reloaded FE, I get same pic as before. Does not drop into Autoexec, which first instruction is a msgbox.
Renaming the BE works on a different db on this same computer.

[ItsMe]

I think it is safe to say that there is a corrupted object in the database. Which object it is can be anyone's guess. I might guess a system table has an incorrect name reference or something along those lines. I have successfully imported corrupt tables and queries before.

[JamesDeckert]

Wouldn't creating a new db and importing the db tables, etc rebuild the system tables?
Is there a way to cause the system tables to be rebuilt?

[ItsMe]

Wouldn't creating a new db and importing the db tables, etc rebuild the system tables?

In some cases, yes. However, I have experienced the need to rebuild a table or rebuild a query in order for symptoms to go away. In those cases, I can only assume incorrect information was stored in the system tables.

Is there a way to cause the system tables to be rebuilt?

It may not be the System tables. I would suspect Importing the objects to a new DB would eliminate issues with the system tables. However, some information may still be brought over with Relationships and stuff like that.

As for rebuilding them, you can take a look at them. One instance where I had an issue with a query object, it was storing incorrect data regarding the names of forms used in where clauses. I kept rebuilding all of the forms and the problem did not go away until I rebuilt the one query. For something like that, I would not expect the problem to be with the query. So I would not even know how to guess where, in the system tables, such an issue could be resolved. It seemed to be an issue with storing the wrong index from the Forms collection.

So, if you did not use the advanced options to import extra stuff like import procedures, relationships, etc. I am not sure what else is left. The fact that you can compare one database file to the problem file indicates there is still something wrong with and inside the problem file.

[JamesDeckert]

So, if you did not use the advanced options to import extra stuff like import procedures, relationships, etc.

I don't know what advanced options you're talking about. I imported tables/queries/forms/reports/macros/modules. All items on each tab.
In the options button, the relationships checkbox was defaulted on. The other boxes stayed unchecked.

I think I'm going to try this over again, but leaving out all queries, etc and see if I can get the autoexec to run. Try to narrow it down, if indeed there is a problem in one of the objects.

[ItsMe]

...but leaving out all queries, etc and see if I can get the autoexec to run. Try to narrow it down, if indeed there is a problem in one of the objects.

That is a good idea. You could also uncheck the option to import Relationships. If leaving the relationships behind also leaves the cause of the problem behind, that would be good.

[JamesDeckert]

update: Imported all tables only (no relationships). Problem remains.
Started over. Imported some tables. No problem. Deleted tables that were last imported. Problem remains.
So now narrowing down tables.

BTW. I had system tables displayed in my original db. So when I imported all tables originally, the system tables were displayed to be imported.
But if you hide system tables, they aren't displayed when doing import.