Creepy errors after split - Split Your Database in Microsoft Access


	Back to Split Your Database Comments List

Upload Images Link Email

Creepy errors after split

Thomas Gonder

3 years ago

I've been working on a development db for some months. I've gotten used to the usual run-time errors, and have shaken out several procedures in a form, over and over again and they work fine. After doing a split, several VBA errors occur that seem random, in that they appear once, I view in the debugger, they make no sense, then run again without the error.

Has anyone else experienced this kind of odd behavior? I'm using Access 2021 on Windows 10. I suspect that some of these are timing problems as I'm now using the network to a remote PC. But that doesn't explain VBA code failing with illogical run-time errors I wouldn't think.

	Thomas Gonder OP 3 years ago
As an additional note, I routinely compress and repair and decompile, even did these just before the split.

	Kevin Robertson 3 years ago
What are the error messages? When you click debug is there specific code selected?

	Richard Rost 3 years ago
Are you running over a network or on the same PC? Could be a network issue.

	Thomas Gonder OP 3 years ago
Yep, over a network, and VBA run-time errors occur that don't make any sense. A lot of the time I get "Access not responding" title bar. This is crazy given it's a local network that is fast enough for almost anything the WEB can throw at it, including HD streaming.

	Adam Schwanz 3 years ago
Just remember LAN and WAN aren't the same thing. You could have a great connection to the internet but not be able to reach or have delays to get to a location on the LAN for a million possible reasons at the same time. Is this database split then? If so, where is the backend stored?

	Kevin Yip 3 years ago
HI Thomas, what exactly were the error messages, and what was the code that caused them? We need to look at those to determine what happened. If the errors occurred after you split the database, then the split may have something to do with this. Maybe the split wasn't done correctly and some of your data are inaccessible.

	Thomas Gonder OP 3 years ago
I was doing a quick demo of split. So, I didn't have time to capture everything. Next time I'll be more thorough in documenting the VBA errors I'm seeing after a split.

This thread is now CLOSED. If you wish to comment, start a NEW discussion in Split Your Database.