Referencing saved query field name [∆-Dawn] in a procedure?

[yeah]

Interestingly enough, ∆-time: [TDstamp]-[TD] works in the query-builder making "∆-time" a valid calc'd field header [∆-time] in a saved query. Butcha can't create qry-def in VBA code using it as a field name. Nor can U-reference it in a DLookUp in a procedure. U-can save "∆-time" string value in a table field. U-can even use "∆-Dawn" as a table fieldname [∆-Dawn]. Anyone know how to reference [∆-Dawn] query field name in a procedure using DLookup?

[June7]

You have a symbol in a field name? Never seen this before. Recommend changing. Really should not use spaces nor punctuation/special characters (underscore only exception) in naming convention.

I tested that field name with DLookup() in a query and it works. However, DLookup() in VBA has issue. VBA can't render the character.

[yeah]

Thanks for the input. If I wanted to change it, I would. What I do want to do is find a work-a-round that may enable VBA to deal with it. Any ideas?

[isladogs]

You could try using the ASCII character code for the delta symbol in your vba code though I've no idea whether that will work.
Otherwise I think you will have to change it or not use it in vba.

[yeah]

Thanks much. I know of no ASCII code for ∆ I could be mistaken. But I cannot find an ALT-code for it. Meanwhile, am enjoying the challenge of seeking work-a-round.

[June7]

None. VBA can't read the character. Period.

Why so insistent this symbol used in field name? Experienced database developers will not use punctuation/symbols in naming convention (with exception of underscore).

[yeah]

I'm not sure 'insistent' is the adjective I would have chosen. Admittedly, I'm curious why VBA won't crunch it. And it order to find out why not, it's actually quite handy to keep trying. Perhaps it's worth mentioning that I don't plan on recommending it to the experienced database developer community as a breakthrough in naming convention alternatives. If you'd like to help figure this out, join in. But U R not gonna convince me not to try simply because it's unconventional. U C, I already know that and I'm trying anyway. That's all there is to it.

[isladogs]

I've just checked the ASCII list and it isn't included though many Greek letters are. I think chr 235 is a small delta but that's no help.
I think there is an obvious work round but it's the one you seem unwilling to make.

I wish you luck but suspect it's going to be a waste of your time in the end

[yeah]

I'm not doing it for a customer. I'm on a quest for knowledge. If there's a work-a-round, I'll find it. If not, I'm on to something else.
if SQL can process SELECT tblPrgmrNotes.PgmrNote FROM tblPrgmrNotes WHERE (((tblPrgmrNotes.PgmrNote) Like "*∆*"));
then I'm a little bit curious as to whether there exists a work-a-round that'll make it happen in VBA.

[Micron]

Pretty sure vba doesn't support Unicode - not even with Option Compare Binary. While there are functions like ChrW that I don't know much about, they seem to be intended for converting unicode values to decimal or whatever, but the character source is usually a table or spreadsheet. Thus you likely can process the character, but not by explicitly typing it into the vba editor. The editor will represent it as ? because it's not supported.

[yeah]

Pretty sure vba doesn't support Unicode - not even with Option Compare Binary. While there are functions like ChrW that I don't know much about, they seem to be intended for converting unicode values to decimal or whatever, but the character source is usually a table or spreadsheet. Thus you likely can process the character, but not by explicitly typing it into the vba editor. The editor will represent it as ? because it's not supported.

Thx 4 the input. I tend 2 agree and that's the direction I'm headed in. gonna keep pluggin' away

[isladogs]

Actually VBA can handle unicode at least in the following context
I work with importing JSON files into Access & to do so I need to detect the file's tristate level - the most common is true (unicode) but some are false (ascii) or mixed(!)

JSON files are of course just text files and you can edit the tristate level of any text file in Notepad, then click Save As and changing the encoding setting Unicode being one option.

And I just looked at a JSON file I made with deliberately difficult characters to see if Access could import them to a table - it can!
And for what its worth look at the symbol I highlighted in the screenshot



If anyone cares, you can look at the attached JSON file renamed as txt for uploading

[Micron]

Yes, and you can paste that symbol directly in to a table, and as the OP stated, use it in a query as well. My point was that you can't use it in vba construct.
Thus you likely can process the character, but not by explicitly typing it into the vba editor

[orange]

See this link for M$oft's thinking on naming rules.