My project has grown for a year and now comprises of 19 standard modules, 7 class modules 11 forms. Some of the forms appear to freeze when called but, in fact, they are just slow to respond, taking a couple of minutes, regardless of what is clicked, e.g. just a change of focus or triggering an e...
@FreeMan it's possible that these errors are red herring. There could be some completely unrelated failure occurring during the parse and so it reports where it was in the parse when the error occurred. I would begin to look at the environment. Server resources, network failures, other factors unique to your environment.
> One point to mention in all this is that there seem to be some things like "Excel-isms" involved in these ATTRIBUTE lines, most especially the VB_INVOKE_FUNC area. Without making a more exhaustive search into the other Office (and related) apps, and how their generated/exported VBA modules utilize the ATTRIBUTE "feature" differently, I'm not sure we'll get the whole picture or be able to properly define what these things may really do.
Yeah, save early, save often. Except when I forget... Save AutoRecover information is on and set to 10 min, but it still didn't offer to give me the most recent recovery file.
:(
Plus, working via VPN it's often extremely slow to open/save/close files, especially Excel. No idea why...
le sigh... At least I've got something to keep me busy tomorrow.
Whoa whoa whoa, guys. Hold the press. I just found a little note on the MSAccess development roadmap that says Access is getting a new SQL editor based on Visual Studio Code!!
VBA Rubberducking
VBA Rubberducking