Odd Slowdown between Prod & Test versions

[The_Doc_Man]

I have a split Front End/Back End pair. To work on them, I have further made copies for a DEV folder and separate copies for a production folder. I have a local copy of the BE for the DEV copy. When I promote code from DEV to production, I always use the Linked Table Manager as part of the promotion to point the FE to the shared BE copy over the network. I do it this way because our network is very slow and I need to avoid wasting time in the BE DEV copy.

I ran into a snag that forced me to make a separate TEST copy that points to a private TEST BE that is also on the same disk (but another folder) as the production copy. The test copy is like the DEV copy in that I can edit/compile code with it (it is not yet a MDE or ACCDE) but it points to a back-end that it found over our slow network. So...

I had to edit something to fix a minor bug. I then compiled and saved the code in this test copy - and instead of taking seconds, it took minutes. No forms were open in form view. Only one form was open in design view, the one for which I was updating a code snippet. So what is it updating on the BE if nothing was explicitly open?

P.S. - Windows Task Manager's network screen confirms that before I do the compile and save, there is no activity. When I start the SAVE operation after the compilation, I see some network activity. So what am I updating in the BE if no forms are open in anything other than design view?

 

[WayneRyan]

Hi Doc,

I don't think you're trying to update the BE during the save.

I do think that the FE is checking BE tables that are referenced by your form.
That is probably the SLOW activity you're seeing.

Happy Holidays,
Wayne

 

[The_Doc_Man]

Thanks, Wayne. I sort of figured that it was something like that. But if all I updated was VBA code, not a static query definition, then Access doesn't know whether any of my dynamic queries are being edited. (Which in this case they weren't.) So... what's to check, I wonder?

More to the point, is there a flag I missed in the options that would tell it to not waste time verifying the BE for every frimpin' compile? I didn't see one and don't know if there is a way to suppress that behavior. OK, for the novice, I could see a revalidation of all tables - but maybe I would like to have the option. I'll do some research on this to see what I can find, but I'm not going to hold my breath on this one.

 

[WayneRyan]

Doc,

I think its checking your bound forms, combo boxes, etc.

Get your form in Design View and see if you can rename one of the tables
in the BE. I think they're being referenced.

Wayne