Global Const (MY_VERSION$) 's value will not display in textbox

[MLH]

I have 2 global constants declared in the same global module:
Global Const MY_VERSION$ = "1.04"
Global Const ProjectName$ = "MyProj"

I have 2 global procedures designed to return the
value of these 2 constants...

Function GetCurrentRev() As String
GetCurrentRev = MY_VERSION$
End Function

Function GetProjectName()
GetProjectName = ProjectName$
End Function

I have 2 bound textbox controls on the same form
(frmAdminDoListEntryForm)
referencing the above 2 functions in the 2 textbox's DefaultValue
property. One textbox is named Text106 and the other ProjNameBox. They
are bound to [Rev] and [ProjName] query fields respectively and the
form itself is bound to qryAdminDoList.

When I go to a new rec on that form, the 2 textboxes display #Name?
and "MyProj" respectively. I'm trying to determine why one textbox
displays the value of a global string var and the other does now? If I
run either of the functions in the immediate window - each displays
the expected value of the related global constant. I see these two
textboxes and their related functions and values as virtually
identical and have no earthly idea why one is working and the
other is not.

My earlier thread on this subject was perhaps mis-titled and I'm
picking up from here. After reading this post, if you still think I'm
asking "What's the meaning of #Name?" then feel free to bow
out of this thread.

[rkc]

MLH wrote:

I have 2 global constants declared in the same global module:
Global Const MY_VERSION$ = "1.04"
Global Const ProjectName$ = "MyProj"

I have 2 global procedures designed to return the
value of these 2 constants...

Just for kicks, create a new form with nothing but two
textboxes on it and see if you can get them to work with
your functions.

[Randy Harris]

"rkc" <rk*@rochester.yabba.dabba.do.rr.bomb> wrote in message
news:PW********************@twister.nyroc.rr.com.. .

MLH wrote:

I have 2 global constants declared in the same global module:
Global Const MY_VERSION$ = "1.04"
Global Const ProjectName$ = "MyProj"

I have 2 global procedures designed to return the
value of these 2 constants...

Just for kicks, create a new form with nothing but two
textboxes on it and see if you can get them to work with
your functions.

Or - exchange the default value between the controls. That will tell you if
the problem is the control or the function. (Note: one of your functions
returns a string, the other a variant)

[MLH]

Well, you are certainly on to something there, rkc. I did
what you said and the textboxes worked FINE with the
same two functions. That sure leaves me in a rut, as I
have no earthly idea what could be going on in my first
form to contribute to this behavior. Thx 4 the heads up!
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Just for kicks, create a new form with nothing but two
textboxes on it and see if you can get them to work with
your functions.

[MLH]

I was intrigued by the suggestion. I did exchange the default value
between the two controls. The behavior was the same. Yes, sad,
but true. Of course, the controls were reversed and each one
displayed what was previously displayed in the other.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Or - exchange the default value between the controls. That will tell you if
the problem is the control or the function. (Note: one of your functions
returns a string, the other a variant)

[MLH]

I even went so far in the new form as to rename the two
textbox controls to odd names - one qwertyu and the other
asdfghjk. Still, the form worked perfectly, with both controls
displaying EXACTLY what one would expect them to show
when going to a new record - the default values of the 2
global constants.

Just for kicks, create a new form with nothing but two
textboxes on it and see if you can get them to work with
your functions.

[rkc]

MLH wrote:

I even went so far in the new form as to rename the two
textbox controls to odd names - one qwertyu and the other
asdfghjk. Still, the form worked perfectly, with both controls
displaying EXACTLY what one would expect them to show
when going to a new record - the default values of the 2
global constants.

Open your new form and your troublesome form.
Delete the textboxes on the troublesome form.
Copy and paste the textboxes from your new form to your
troublesome form.

[Randy Harris]

If the problem switched, you have something wrong with your control. Just
recreate it. Or, as rkc suggested, copy it from the working form.

"MLH" <CR**@NorthState.net> wrote in message
news:r6********************************@4ax.com...

I was intrigued by the suggestion. I did exchange the default value
between the two controls. The behavior was the same. Yes, sad,
but true. Of course, the controls were reversed and each one
displayed what was previously displayed in the other.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Or - exchange the default value between the controls. That will tell you ifthe problem is the control or the function. (Note: one of your functions
returns a string, the other a variant)

[MLH]

I did it, crossed my fingers and all that good stuff.
Same problem. Believe me, I've deleted and recreated
those two controls so many times - its not even funny.
I think I may copy the form to a temporary working copy,
trash one object at a time from the copy - testing the form
after each deletion to see if any object may be singled out
as the offending object. Its quite frustrating, actually.

I'm confident that its something simple that is being overlooked.
In a brand new form, it works. So, the issue is most certainly
form-specific.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Open your new form and your troublesome form.
Delete the textboxes on the troublesome form.
Copy and paste the textboxes from your new form to your
troublesome form.

[MLH]

On Wed, 02 Nov 2005 00:43:25 GMT, "Randy Harris" <ra***@SpamFree.com>
wrote:

If the problem switched, you have something wrong with your control. I'm not sure I understand. I had (A) a working control and (B) a non-
working control. I switched their default values. I then had (A) a
nonworking control and (B) a working control. That seems to suggest
to me that, depending on what default value property setting EITHER
control has - both can be working or non-working. I think that means
the controls both work. Its just that any control with
=GetCurrentRev() as its default property setting does not work. I tend
to think its that setting that is the problem rather than the control.
Does that make sense?
Just recreate it. Or, as rkc suggested, copy it from the working form.

[Randy Harris]

"MLH" <CR**@NorthState.net> wrote in message
news:39********************************@4ax.com...

On Wed, 02 Nov 2005 00:43:25 GMT, "Randy Harris" <ra***@SpamFree.com>
wrote:

If the problem switched, you have something wrong with your control.

I'm not sure I understand. I had (A) a working control and (B) a non-
working control. I switched their default values. I then had (A) a
nonworking control and (B) a working control. That seems to suggest
to me that, depending on what default value property setting EITHER
control has - both can be working or non-working. I think that means
the controls both work. Its just that any control with
=GetCurrentRev() as its default property setting does not work. I tend
to think its that setting that is the problem rather than the control.
Does that make sense?

Just recreate it. Or, as rkc suggested, copy it from the working form.

You're right, I didn't think it through. If you get the problem with that
function regardless of which control you use, then the problem must be with
the function. I don't know why it would matter, but change the data type as
I suggested earlier.

[Trevor Best]

MLH wrote:

I did it, crossed my fingers and all that good stuff.
Same problem. Believe me, I've deleted and recreated
those two controls so many times - its not even funny.
I think I may copy the form to a temporary working copy,
trash one object at a time from the copy - testing the form
after each deletion to see if any object may be singled out
as the offending object. Its quite frustrating, actually.

I'm confident that its something simple that is being overlooked.
In a brand new form, it works. So, the issue is most certainly
form-specific.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Long Shot: Check the code behind that form and make sure it doesn't
contain anything like:
Function GetProjectName()
GetProjectName = "#Name?"
End Function
;-)

Actually, while it's displaying #Name? Can you edit the field?

Create new form, copy all the good bits from old form.

[lylefair]

Did you actually look at the bound "property" of the control which
shows #Name, ie the property that connects it with a field in the
form's recordset. Are you sure the field to which you have bound the
control actually exists; are you sure there is no syntax error in your
defining this?

[rkc]

MLH wrote:

I did it, crossed my fingers and all that good stuff.
Same problem. Believe me, I've deleted and recreated
those two controls so many times - its not even funny.
I think I may copy the form to a temporary working copy,
trash one object at a time from the copy - testing the form
after each deletion to see if any object may be singled out
as the offending object. Its quite frustrating, actually.

You're using the functions as the Default Value property
of the controls, correct?

Did the #Name error occur before or after you set the
Control Source property of the controls you cut & paste?
Did you even try the form before you did?

[David W. Fenton]

MLH <CR**@NorthState.net> wrote in
news:ut********************************@4ax.com:

I'm confident that its something simple that is being overlooked.
In a brand new form, it works. So, the issue is most certainly
form-specific.

Do you have anything in the problematic with the same name as the
function you're calling?

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[MLH]

>Long Shot: Check the code behind that form and make sure it doesn't

contain anything like:
Function GetProjectName()
GetProjectName = "#Name?"
End Function
;-) Search of code in all procedures on form reveals no occurrences
of the string "GetProjectName"

Actually, while it's displaying #Name? Can you edit the field? No, I cannot. Tried to while displaying existing records as well
as blank new record. Cannot edit. Does that provide a clue?
Create new form, copy all the good bits from old form.

Will do 'n get back to the NG after doing so.

[MLH]

>Did you actually look at the bound "property" of the control which

shows #Name, ie the property that connects it with a field in the
form's recordset. Are you sure the field to which you have bound the
control actually exists; are you sure there is no syntax error in your
defining this?

Just to be sure, I deleted the controls from the form and recreated
them by dragging them from the Field List to the form. The form was
created months ago. Although I cannot explicitly recall having done
it this way in the beginning, its a habit of mine & highly likely I
did it just that way initially.

[MLH]

>You're using the functions as the Default Value property

of the controls, correct? Yes
Did the #Name error occur before or after you set the
Control Source property of the controls you cut & paste?

OK, you're on to something here. I killed the problematic
control. Then I re-drug it from the Field List back onto the
form and opened the form in Form view before assigning
a default property to the control. The #Name? error condition
is displayed in the control even without the default value
property setting. I'm not sure what you're on to, but you are
definitel on to something.

[MLH]

Not sure that I understand the question. But there is nothing in CBF
on the form of the same name as the function being called.

Do you have anything in the problematic with the same name as the
function you're calling?

[MLH]

GetCurrentRev() is the function called by the DefaultValue property
of the problematic control. The GetCurrentRev() function is being
called by the non-problematic control. And, further checking proves
NEITHER function name appears anywhere in the CBF.

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Long Shot: Check the code behind that form and make sure it doesn't
contain anything like:
Function GetProjectName()
GetProjectName = "#Name?"
End Function
;-)

Actually, while it's displaying #Name? Can you edit the field?

Create new form, copy all the good bits from old form.

[MLH]

For Christ's sake! I've got my head so far up my ass! Here's what I
should have said.

GetCurrentRev() is the function called by the DefaultValue property
of the problematic control. The GetProjectName() function is being
called by the non-problematic control. And, further checking proves
NEITHER function name appears anywhere in the CBF.

With my head up my ass as far as it was, I must have been having
difficulty reading what I was typing.

[MLH]

And, in case the next thing you are curious about is
whether I can edit the field values DIRECTLY in the
source query - the answer is yes, I can. Somehow,
on the form, though - I cannot.

[rkc]

MLH wrote:

You're using the functions as the Default Value property
of the controls, correct?

Yes

Did the #Name error occur before or after you set the
Control Source property of the controls you cut & paste?

OK, you're on to something here. I killed the problematic
control. Then I re-drug it from the Field List back onto the
form and opened the form in Form view before assigning
a default property to the control. The #Name? error condition
is displayed in the control even without the default value
property setting. I'm not sure what you're on to, but you are
definitel on to something.

So try the opposite. Delete the textbox. Add a new one from the
toolbox and set the default property without setting the ControlSource.
If it works O.K. with the Default Property, try setting the control
source from the textbox property sheet. If it doesn't work after
setting the control source, I'd have to say your form is toast.

Maybe a de-compile? I don't know enough about what that fixes to
say.

I think I'd just shitcan the form and start over.

[MLH]

Well, I deleted every single control off the form,
one-at-a-time, deleting each control's code first.
When the very last thing left was the problematic
control itself, I opened the form. Same problem.
So, I deleted that control, bringing the form to an
empty state - as empty as I could get it. Then, I
added the desired textbox control back again.
Opening the form - same problem.

So, I took a slightly different approach. I opened
the original form with the problematic control. I clicked
the button to view code. I chose select all and pressed
the delete button. Opening the form thereafter - everything
worked just fine. The problematic control was no longer
problematic - that is, until I pasted the code back in.
Now I had the code and all controls deleted, one-by-one
in a slow & painful process first and when I got to the very
fuckin' end - the problem persisted. If I just show code,
hit select and and the delete ke - removing the code but
leaving all the controls - the problematic control seems to
be resolved. Hmmm??? dunno

[MLH]

Trevor, I might have narrowed it down to this procedure...

Private Sub Form_Current()
'************************************************* ****************
' Added this code 12/24/2001 - long after this form's birth. Its
' purpose is to make a button visible if there is a graphic assoc-
' iated with the current Do-Item record. It also determines the
' current record number 'n displays it on the form.
'
' The only way I can tell if a graphic is in the [Pic] field is to
' try to assign the field value to a variable. For instance:
' MyVariant = DLookup("[Pic]", "tblDoItems", "[DoItemID]=495")
' DoItem #495 does NOT have a picture in it. The above line does
' NOT produce an error when run. However, take a look at this:
' MyVariant = DLookup("[Pic]", "tblDoItems", "[DoItemID]=497")
' DOES produce an error (#2004, "Out of Memory") when its executed.
' So, I'll just trap that error number and...
'
'************************************************* ****************
On Error GoTo Form_Current_Err:
Dim ThisForm As String, MyVariant As Variant
Dim CheckingForPic As Integer, PicInRec As Integer
ThisForm = Me.Name
PreviousDoItem = CurrentDoItem
If Not IsNull(Me!DoItemID) Then CurrentDoItem = Me!DoItemID Else
CurrentDoItem = 0

CHK4APIC:
CheckingForPic = True
MyVariant = DLookup("[Pic]", "tblDoItems",
"[DoItemID]=Forms!aa!DoItemID")
CheckingForPic = False

SETCAMERAVISIBILITY:
If PicInRec = True Then
PictureClicker.Visible = True
Else
PictureClicker.Visible = False
Pic.Visible = False
End If

SHOWHICHREC:
Dim WhichRec As Integer
WhichRec = GetFormRecNum(Me)
RecNum.Caption = "#" & str$(WhichRec)

ExitForm_Current:
Exit Sub

Form_Current_Err:
If Err = 3021 Then Resume Next '3021 error is "No Current
Record" and was popping up each time I went to new rec
If Err = 2004 And CheckingForPic = True Then
PicInRec = True ' Error
#2004 is out of memory error caused by
Resume Next '
assigning [Pic] field value to a variable
End If
Dim r As String, k As String, Message3 As String
r = "The following unexpected error occurred in Sub Form_Current,
CBF on " & ThisForm & "."
k = CRLF & CRLF & str$(Err) & ": " & Quote & Error$ & Quote
Message3 = r & k
MsgBox Message3, 48, "Unexpected Error - " & MyApp$ & ", rev. " &
MY_VERSION$
Resume ExitForm_Current

End Sub

Anybody see anything wrong with this procedure that could be
causing my problem???

[lylefair]

MLH wrote:

Anybody see anything wrong with this procedure that could be
causing my problem???

I think the procedure makes insufficient provision for prayer.

[Trevor Best]

MLH wrote:

Actually, while it's displaying #Name? Can you edit the field?

No, I cannot. Tried to while displaying existing records as well
as blank new record. Cannot edit. Does that provide a clue?

The clue this provides is that the name of the field the control is
bound to is mis-spelt.

[Trevor Best]

MLH wrote:

Trevor, I might have narrowed it down to this procedure...

Private Sub Form_Current()
'************************************************* ****************
' Added this code 12/24/2001 - long after this form's birth. Its
' purpose is to make a button visible if there is a graphic assoc-
' iated with the current Do-Item record. It also determines the
' current record number 'n displays it on the form.
'
' The only way I can tell if a graphic is in the [Pic] field is to
' try to assign the field value to a variable. For instance:
' MyVariant = DLookup("[Pic]", "tblDoItems", "[DoItemID]=495")
' DoItem #495 does NOT have a picture in it. The above line does
' NOT produce an error when run. However, take a look at this:
' MyVariant = DLookup("[Pic]", "tblDoItems", "[DoItemID]=497")
' DOES produce an error (#2004, "Out of Memory") when its executed.
' So, I'll just trap that error number and...
'

If I were you I'd check for:
DCount("*", "tblDoItems", "[DoItemID]=497 And [Pic] is not null")

[MLH]

On Fri, 04 Nov 2005 08:12:16 +0000, Trevor Best
<no****@localhost.invalid> wrote:

MLH wrote:

Actually, while it's displaying #Name? Can you edit the field?

No, I cannot. Tried to while displaying existing records as well
as blank new record. Cannot edit. Does that provide a clue?

The clue this provides is that the name of the field the control is
bound to is mis-spelt.

Hmmm??? The form is bound to qryAdminDoList...
SELECT DISTINCTROW tblDoItems.DoItemID, tblDoItems.Title,
tblDoItems.Details, tblDoItems.Done, tblDoItems.Priority,
tblDoItems.EntryDate, IIf([Priority]=1,"High
Priority",IIf([Priority]=2,"Medium Priority","Low Priority")) AS
PriorityWord, tblDoItems.ProjName, tblDoItems.Pic, tblDoItems.Rev
FROM tblDoItems
WHERE (((tblDoItems.ProjName)=GetProjectName()))
ORDER BY tblDoItems.Priority;

tblDoItems is an attached table. Here are the fields recursed in the
immediate window...
Fields in tbldoitems:

DoItemID
Title
Details
Done
Priority
EntryDate
ProjName
Pic
Rev

It looks like the spelling is OK. I sure hope I'm not stepping on
another reserved word in my code somewhere. Such violations
are quite sneaky in the way they surface as errors. I have opened
a brand new form, BTW, copied & pasted the problematic control
from subject form to new form, set the form's recordsouirce to the
query then opened. All is AOK when done that way.

But I do have a prob w/ code somewhere. I can create a new
form, paste in all the controls (but none of the code) and the form
works perfectly.The problematic textbox is NOT a problem at all.
But, if I cut 'n paste the code from the old form ( I even saved the
code to text file, opened that, using it as a source) - the erroneous
condition re-emerges. I just don't know what to look for in the code
to finger the problem.

[MLH]

I failed to mention that I ported this app over
from A2.0 - grasping for straws at this point - dunno
if that makes for anything worth considering.

[rkc]

MLH wrote:

Well, I deleted every single control off the form,
one-at-a-time, deleting each control's code first.
When the very last thing left was the problematic
control itself, I opened the form. Same problem.
So, I deleted that control, bringing the form to an
empty state - as empty as I could get it. Then, I
added the desired textbox control back again.
Opening the form - same problem.

Care to zip the .mdb and email it?

[David W. Fenton]

MLH <CR**@NorthState.net> wrote in
news:q3********************************@4ax.com:

Not sure that I understand the question. But there is nothing in
CBF on the form of the same name as the function being called.

Is there any object of any type with a conflicting name?

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[David W. Fenton]

MLH <CR**@NorthState.net> wrote in
news:r1********************************@4ax.com:

I failed to mention that I ported this app over
from A2.0 - grasping for straws at this point - dunno
if that makes for anything worth considering.

I've never tried to set a default control value from a Global
constant. Why not get rid of the whole problem by making the *table*
have the default value that's stored in the constant?

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Trevor Best]

David W. Fenton wrote:

MLH <CR**@NorthState.net> wrote in
news:r1********************************@4ax.com:

I failed to mention that I ported this app over
from A2.0 - grasping for straws at this point - dunno
if that makes for anything worth considering.

I've never tried to set a default control value from a Global
constant. Why not get rid of the whole problem by making the *table*
have the default value that's stored in the constant?

It's easier to change in code than in a table (multiple tables?)

Another approach is to have no default value in the form but use the
BeforeInsert event to populate the controls.

[David W. Fenton]

Trevor Best <no****@localhost.invalid> wrote in
news:43*********************@news.zen.co.uk:

David W. Fenton wrote:

MLH <CR**@NorthState.net> wrote in
news:r1********************************@4ax.com:

I failed to mention that I ported this app over
from A2.0 - grasping for straws at this point - dunno
if that makes for anything worth considering.

I've never tried to set a default control value from a Global
constant. Why not get rid of the whole problem by making the
*table* have the default value that's stored in the constant?

It's easier to change in code than in a table (multiple tables?)

Another approach is to have no default value in the form but use
the BeforeInsert event to populate the controls.

Or set the Default Value to a leteral string upon opening the form.

Of course, it's clear at this point that the problem isn't with the
default value function but with the underlying controlsource.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[MLH]

Thx, Trevor. Back in the Access 2.0 days, I had difficulty determining
whether there was anything in the [Pic] Ole Object field. I don't know
why. Many moons past, granted, but I remember I could not
seem to determine whether something was stored in the field
quite so easily there. Here's an old dead thread in which Turtle
tried to help me out...

http://groups.google.com/group/comp....e212ec87165?q=[pic]mlh&rnum=1#8f3c4e212ec87165

But I just tried the line you gave me in Access 2.0 and it WORKED.
Dunno why I didn't use it then.

And, in A97 - no prob whatsoever...
I just tried ?DCount("*", "tblDoItems", "[Pic] is not null") in the
immediate window and it returned 26. That seems about right.
?DCount("*", "tblDoItems", "[Pic] is null") returns 776. So in
A97, seems to be a breeze. That was not the case in 2.0.
Thx for the 'heads up' on the issue.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

'
' The only way I can tell if a graphic is in the [Pic] field is to
' try to assign the field value to a variable. For instance:
' MyVariant = DLookup("[Pic]", "tblDoItems", "[DoItemID]=495")
' DoItem #495 does NOT have a picture in it. The above line does
' NOT produce an error when run. However, take a look at this:
' MyVariant = DLookup("[Pic]", "tblDoItems", "[DoItemID]=497")
' DOES produce an error (#2004, "Out of Memory") when its executed.
' So, I'll just trap that error number and...
'

If I were you I'd check for:
DCount("*", "tblDoItems", "[DoItemID]=497 And [Pic] is not null")

[Trevor Best]

David W. Fenton wrote:

It's easier to change in code than in a table (multiple tables?)

Another approach is to have no default value in the form but use
the BeforeInsert event to populate the controls.

Or set the Default Value to a leteral string upon opening the form.

But if you have more than one form to get the version number, then you
want to up the version of your code...

[David W. Fenton]

Trevor Best <no****@localhost.invalid> wrote in
news:43***********************@news.zen.co.uk:

David W. Fenton wrote:

It's easier to change in code than in a table (multiple tables?)

Another approach is to have no default value in the form but use
the BeforeInsert event to populate the controls.
Or set the Default Value to a leteral string upon opening the
form.

But if you have more than one form to get the version number,

then you want to up the version of your code...

Eh?

If the version number is stored in a global constant, and you want
to create records that record that version number, setting the
default value of the control to the literal string at runtime when
you open the form (in the OnLoad event, rather than the OnOpen,
because controls are not always available during OnOpen) sounds
like
an awfully efficient way to do it. Then you don't need a UDF for it
at all.

What that has to do with multiple forms, and upping the version
number, I don't know. If all forms use the value in the global
constant to set the default value at runtime, it would seem to me
that changing the global constant will take care of any problems
you
might be alluding to.

Note that when I said:

Or set the Default Value to a leteral string upon opening the
form.

IU did not also say "do that in design mode and save the change."

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Trevor Best]

David W. Fenton wrote:

Note that when I said:

Or set the Default Value to a leteral string upon opening the
form.

Sorry, I missed that bit, probably too busy musing over your typo :-)