[AccessD] OpenArggggggghhhhhhsssss

David McAfee davidmcafee at gmail.com
Thu Aug 11 11:56:39 CDT 2011


Access 2007?

I've been having very weird issues with OpenArgs being null from time to
time.

I put an optional stop on the first line and know that I sent it an argument
and it still shows null.

I haven't seen it happen in a while, but it was driving me nuts when it did.

try calling the form open from the immediate window and place an optional
stop in the forms open event and step through each line.

It is possible Access doesn't think your openArgs is a string.

D

On Thu, Aug 11, 2011 at 9:32 AM, William Benson (VBACreations.Com) <
vbacreations at gmail.com> wrote:

>
> I am sending a nonempty string to openargs but when the form is closing I
> call a subprocedure on the form which is closing -- and when that procedure
> refers to OpenArgs, it is frequently null for reasons which I cannot
> understand....? So I tried assigning the openargs to a module level string
> variable instead, on _Load. I saw that the OpenArgs was null in that
> assignment statement, throwing an error. So I checked the call stack, went
> to the line of code which was opening the form, and saw that it was fine -
> the strOpenArgs variable I was passing as the value for the OpenArgs
> argument was a populated string. Anyone seen this?
>
> My workaround is to give up on OpenArgs and resort to a global string
> variable.
>
> Thanks
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>



More information about the AccessD mailing list