Creating an Execute-Only Database -- Project Compile Issues

[Neophite]

I have a DB with two distinct navigation forms for two classes of users. Each navigation form contains a couple of dozen forms which almost all load global variables during the form on-load event; these global variables are created/populated during the login event. In addition, there are buttons within many of the forms that are disabled upon the click event -- Y/N fields, create record, change/update record, etc. Everything works fine and dandy -- slick as a whistle. When I run Compile Project it pukes because all global variables required for the form on-load events are apparently null (absent the login event having occurred during the compile process), which appears to be no-no from a compile perspective, and, also the dis-enabling buttons seems to be another big no-no from a compile perspective, so, the compile stops dead in its tracks wherever the VBA code has one of these situations. Thus, the bigger issue is that I am not able to get through the compile process to turn my creation into an Execute-Only database. Oh, what to do?

[RuralGuy]

Are you saying the compiler stops with an error when you try and compile? Variables do not require a value when you compile.

[Neophite]

Are you saying the compiler stops with an error when you try and compile? Variables do not require a value when you compile.

I think the problem is that in most forms I use a click event which triggers the VBA to create/save records to tables, and during the compile the compiler stops wherever it thinks I have used what are at the time of the compile null fields. So, when I try to compile to make for example an executable version, it stops at the first occurrence of one of these null fields, game over. At different times along the way, I went through the login routine -- where the global variable get populated in a Navigation form (two Navigation forms that are used, but it seems that one can only open/active at a time) -- and it compiles until it reaches the null fields in the forms/VBA record events that exist in the second un-opened Navigation form. And, I then reversed the order in order to compile that which would not compile in the first go-round. So, basically everything compiles, but not in mass.

[RuralGuy]

I guess I'm a bit confused. I was not aware you have any control over the order the compiler takes to compile. Would it be possible to post your db here for review? Compact and Repair first and the ZIP it up for posting. Remove any sensitive data of course.

[Neophite]

I guess I'm a bit confused. I was not aware you have any control over the order the compiler takes to compile. Would it be possible to post your db here for review? Compact and Repair first and the ZIP it up for posting. Remove any sensitive data of course.

I can't post it -- security sensitive processes and information. I could email, but first I need to know something about you, e.g., are you a Microsoft employee, which would likely be okay? Grasshopper doesn't have control over the order of the compile; he has just stumbled through it so many times that he knows the order in which shit happens. He is one with the bowl of spaghetti.

[Neophite]

The private message did not open. However, Shazzam, I managed to fix the error in my ways, and the code/compile, too -- it compiled and it even created an executable database. After thinking about several points you had previously made, e.g., about global variables in the compile process, I figured out that there was something else afoot other than my solution jumping to the phantom global variable problem. After I closed the compiler each time, and then went back and looked at the forms, properties, etc., I then would get error messages galore due to the fields containing global variables being cleared in the process. So, I methodically went through the compile and whenever and wherever the compiler puked, I either moved the snippet of code to where it logically belonged in the sequence of events (if it was out of sequence -- before its time), re-wrote it, or deleted it because it was redundant, a lame duck or it had outlived its intended purpose. Problem solved -- pilot error. Perhaps you should go by Rural Yoda.

[RuralGuy]

Excellent! It is *always* better if you can track down and solve your own issues. Much more to learn that way.