Problem Converting .ACCDB to .ACCDE using Access 2016

[CD Tom]

My program searches through all drives on the computer looking for the _be.accdb database, this allows the user to put the database on a network drive. The program when compiled was working fine, but the last time I compiled it and ran it using Access runtime it didn't find the database, however if I run the .accdb program it works fine. What could be the cause of it not finding the database when in a compiled mode.
Any help would be appreciated.

[NeoPa]

Hi Tom.

Can you confirm that all other details are exactly the same when you ran it both times. The likelihood of an ACCDE behaving differently from an ACCDB in the same circumstances is vanishingly small. Before we waste time looking for where a difference may be possible we need vigorous tests run that use all else exactly the same and only the two FE files being different as the ACCDB & ACCDE.

Only if we need to take it further will we need to look at the actual code being run - which you've not included at all at this point anyway.

Logical step by step though. Run the vigorous tests first then we'll take it from there.

[NeoPa]

NB. Compiling is possible with VBA but it's quite different from converting an ACCDB to an ACCDE. I've adjusted the title to reflect this for you.

[CD Tom]

Thanks for the quick response, I'm almost positive that there was no changes to that section of the program. But just to be sure I'm going to compare the previous .accdb and see it there is any difference, I'll let you know if I find anything.

[NeoPa]

Forget that Tom. Why not start with your ACCDB. Test it works. Create an ACCDE from it. Test the ACCDE works. Obviously make no changes to the environment in the mean time. Run the tests from the same place. Do all the usual things to ensure the only possible difference between the two tests is ACCDB & ACCDE files.

[CD Tom]

That's kind of what I did, Opened the .accdb that was working and just made the changes that I made to the one that wasn't working and created the .ACCDE and everything is back working again. Thanks for your help.

[NeoPa]

No worries :-)

Sometimes, just by following the basic steps fastidiously & precisely, we find that things work. This indicates something different that we didn't even notice was involved in the time when it didn't. Something subtle that doesn't even register when we did it / when it happened.

Many good hours get spent chasing after such issues purely for the want of carefully checking & repeating our initial steps. Always a good first step ;-)