William Benson (VBACreations.Com)
vbacreations at gmail.com
Thu Aug 11 13:49:44 CDT 2011
Well OpenArgs and I had rather a bad first date .... and certainly no good night kiss, cheek, forehead, or otherwise. But if I get desperate to use this property again, I will try it the way you've suggested. Thanks! -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Thursday, August 11, 2011 2:30 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] OpenArggggggghhhhhhsssss Assign the variable in the OnOpen event if you're going to use it later in the form. I've never found any other reliable way to reference the OpenArgs later on in any version. Charlotte Foust 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 > > > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com