Running code after edit/add instructions

[Middlemarch]

Code in a module opens a Form thus-

DoCmd.OpenForm "frmSA", acNormal, , , , acDialog, RetVal1

Retval1 is a global variable I use to pass data to the Form OpenArgs. So far so good.

If I make some changes to the code in Form load event, then run the module, the Form always opens/errors with OpenArgs as Null.

I stop the code, sometimes this brings up a Save dialog, but not always. After a Save it works fine.
But sometimes I've already saved the mdb, yet still have to run the code twice for it to work.

Why is this ? Any way to have thing work/run first time? Thanks.

[nrgins]

This shouldn't be happening. Try doing a decompile followed by a compact and repair, and see if it goes away.

[Middlemarch]

It's been happening for years.. just did a decompile and C&R as a test but no change.

[CJ_London]

If I make some changes to the code in Form load event, then run the module, the Form always opens/errors with OpenArgs as Null.

not quite sure what you are referring to here - do you mean the form module? Or the module where RetVal1 is assigned a value?

[Middlemarch]

The Form is called by code in a Module. (code in msg #1).
The Form opens with an error that Openargs is null.

Run it again and it's OK. And remains so until another change to the code, and the cycle repeats.
I just thought just was an Access thing... but it is a pain and be good to be rid of it, if possible.

[CJ_London]

Clearly not all the code is shown - where is the code that assigns a value to RetVal1?

Have you stepped through the code to ensure it is assigned a value?

[Middlemarch]

Retval1 is a string variable but isn't part of the problem.

>Have you stepped through the code to ensure it is assigned a value?

Yes. Nothing changes between getting the error and it working. Same code, same everything.

[CJ_London]

Retval1 is a string variable but isn't part of the problem.

why not? - it is what are passing as the openarg - if it is not assigned a value, it will be null

[hapm]

Changing module code an recompiling code can lead to a project reset, meaning the values of all global vars ar set back to their defaults. Be sure that global variables are still initialized after doing code changes (especially global vars in modules you have changed). It is the same as hitting the cancel button in the "error occured"-debug window or pressing stop in the VBE. As Ajax asked, please provide some hints about when and where you initialize your RetVal1 variable (code appreciated) if you need further help.

[orange]

What is latest status?
Suggest you post a copy of the database --compact and repair, then zip and post --so we can see the details.
Include instructions to get to the problem area.

Good luck.

[Middlemarch]

Thanks for the replies, I'll have a go an duplicating the effect with the smallest mdb and posting here.
Ajax, my OpenArgs is never null as the string is made up -

RetVal1 = Prefix & "$$" & theSerials & "$$" & SA & "$$" & ThisRef & "$$" & Side & "$$" & PrefixSACol
DoCmd.OpenForm "frmSA", acNormal, , , , acDialog, RetVal1

Even if all the variables were reset or null, the $$ delimiters would still exist. I want to use those
values in the Form module and don't know any better way to send them in.

I cannot figure how RetVal1 can even be null, or why it's OK the 2nd time around. It's like Access is refusing
to work properly until some condition is met - and that condition is Save and rerun. Or sometimes just rerun.

[CJ_London]

if you can do the mdb that would be helpful

[CJ_London]

the other thing to clarify is what you are doing with the openargs when the form opens. If you are treating it as an array and then splitting it then an openarg of $$$$$$$$$$ split on $$ would fail to produce an array

[Middlemarch]

In Access 2003 that produces an array of 6 empty strings. But either way it would ensure OpenArgs would not be null.
However I'm unable to replicate the problem as an example. Kind of annoying as I had a mdb ready then removed
a table and module that weren't needed- and it started working. I replaced them and it kept working. However it remains
problematic in the original - which is too big to post. I'll keep trying and it I do get a constant error in something I could post here, I will.

Thanks for the feedback though. One day this might get fixed!

[nrgins]

I've had weird problems like this in Access in the past, where it wouldn't get fixed, even with a decompile. Then, when I deleted something, it got fixed. I guess even the decompile didn't cause all the code to get recompiled, but when I deleted something it did. So my advice to you? Delete in the original whatever you deleted it in the copy, recompile, and then put them back. And see if that fixes the problem. There's something screwy going on with your compilation, that's for sure. Also, sometimes just deleting a block of code, recompiling and then repasting that code back in will solve the problem. Let us know how it goes.