Solved DoCmd.openform (Setting variable default value in destination form) (1 Viewer)

[Jordonjd]

Hi there,
I have several forms (sales order, purchase order, invoice) that all use one "notes" form.
When i click a button on the origin form it opens the "notes" form and populates the "Tbl_Note_Parent_Ref" field with the reference from the origin form
but.. if the origin ref ([crm-1-ref]) is for example "1000-10" instead of populating the "Tbl_Note_Parent_Ref" with the text is calculates and inputs a result so.. "990"

Basically, click to popup the notes form, add the new note, when closed the origin form displays the new note in the note section

Here is the code i am using.

(Notes form)

Private Sub Form_Current()

   If Not IsNull(Me.OpenArgs) And Me.NewRecord Then

      Me.Tbl_Note_Parent_Ref.DefaultValue = Me.OpenArgs

   End If

End Sub

The code for the button on origin form (one fo 3 forms with similar code)

Private Sub Bttn_Add_New_Note_Click()


DoCmd.OpenForm "Frm_Note_Add_New", acNormal, , , acFormAdd, acDialog, [crm-1-ref]


Me.Refresh

End Sub

Im just interested to see if there is a way to utilising the origin field as text only without acces making a calculation of it.

Or if there is a simpler way to have several forms

 

[theDBguy]

Hi. Try it this way:
...
Me.Tbl_Note_Parent_Ref.DefaultValue = """" & Me.OpenArgs & """"
...
Hope that helps...

 

[Micron]

Im just interested to see if there is a way to utilising the origin field as text only without acces making a calculation of it.

IMO the best way is to not use special characters in object names. That [crm-1-ref] looks like a field reference. I had this happen to me many years ago when I didn't know better. Now you do too, I suspect. See

Naming conventions - http://access.mvps.org/access/general/gen0012.htm
https://www.access - programmers.co.uk/forums/showthread.php?t=225837

What not to use in names - http://allenbrowne.com/AppIssueBadWord.html

 

[Gasman]

What about using Cstr()?

 

[Micron]

What about using Cstr()?

You mean as a way of getting around naming things properly?

 

[June7]

@Micron, issue is not with field name (although I agree it is a bad name), it's with the data.

OpenArgs is a variant type so it can hold any kind of data, including Null. CStr() will error on Null. If the field will never be Null, then CStr() should work.

However, I am not able to replicate issue. "1000-10" passes intact.

 

[Micron]

Im just interested to see if there is a way to utilising the origin field as text only without acces making a calculation of it.

@June7; I guess I took it that there must be something (perhaps fields or variables named crm and ref) and that a calculation was being performed when it shouldn't be. If you want to pass [crm-1-ref] to open args and that is a string, it ought to be "[crm-1-ref]" or perhaps "crm-1-ref". If that's totally off the mark, never mind because I'm going to switch from coffee (when I wrote my post) to wobbly pops, in which case I'll make even less sense.

 

[Gasman]

You mean as a way of getting around naming things properly?

No, by way of ensuring that Access sees the value as a string and not a formula?

 

[Jordonjd]

Hi. Try it this way:
...
Me.Tbl_Note_Parent_Ref.DefaultValue = """" & Me.OpenArgs & """"
...
Hope that helps...

HI, that solution works perfectly.

Thanks very much

 

[Jordonjd]

I agree as well, sadly i have filled my DB with badly named objects and yes its a major pain sometimes

Thanks for the all replies

 

[theDBguy]

HI, that solution works perfectly.

Thanks very much

Hi. Glad to hear you got it sorted out. Good luck with your project.