Variables not displaying in DEBUG

[Gary Kissinger]

I encountered a problem today I never saw before - while in DEBUG in a script I typed in variables to display their values and nothing displayed. I've used this feature for years and never had this problem. The script is a straightforward read through a table. I went back to another database and everything worked there. The script does run properly. Version below has debug(0). I was trying to display lastname and age...

'Date Created: 23-Mar-2008 12:43:52 PM
'Last Updated: 25-Mar-2008 04:01:32 PM
'Created By : Gary
'Updated By : Gary

debug(0) ' (0) turns off - (1) turns on

'
' Calculate the age of a child from birthdate to today
'


tbl = table.open("students",FILE_RW_SHARED)
idx = tbl.index_get("lastname")
tbl.index_primary_put(idx)

tbl.fetch_first()
while .not. tbl.fetch_eof()
tbl.change_begin()
tbl.age = age(tbl.birthdate)
tbl.change_end()
tbl.fetch_next()
end while
tbl.close()
debug(0)

[Peter.Greulich]

Re: Variables not displaying in DEBUG

I don't see any variables? Sometimes I find that I have to use the tab key after typing in the var in the debugger. That seems to activate the value display when it's misbehaving.

Not a big deal, I think, but my own preference would be to do this:

tbl.fetch_first()
while .not. tbl.fetch_eof()
[B][COLOR="Red"]vBirthDate = tbl.birthdate[/COLOR][/B]
tbl.change_begin()
tbl.age = age([B][COLOR="Red"]vBirthDate[/COLOR][/B])
tbl.change_end()
tbl.fetch_next()
end while
tbl.close()

[Tom Cone Jr]

Re: Variables not displaying in DEBUG

Gary, aren't "age" and "lastname" table fields? Why do you call them variables? In your other database are you "watching" variables or table fields?

Gary, I found it necessary to have my script store the fieldname values in variables, and then prefix the variable name with "var->"

Here's an example.

[Gary Kissinger]

Re: Variables not displaying in DEBUG

Sorry - I wasn't clear --- I'm referring to keying table names in the fields at the bottom of the DEBUG screen. Yes, you need to tab over the value field to have them display. What's happening here is that no value is ever displayed, only ???

[Stan Mathews]

Re: Variables not displaying in DEBUG

Sorry - I wasn't clear --- I'm referring to keying table names in the fields at the bottom of the DEBUG screen. Yes, you need to tab over the value field to have them display. What's happening here is that no value is ever displayed, only ???

The debugger displays ??? when it can't resolve what you want. You mention keying in table names. Do you really mean fieldnames? And do you key in

tbl.fieldname

using the actual field name? As in

tbl.age
tbl.lastname

[Gary Kissinger]

Re: Variables not displaying in DEBUG

Problem solved !!!! I forgot to prefix the field name with tbl.

I was used to keying in script variables !!!

Thanks!!! I can always depend on this message board to solve my problem!

[G Gabriel]

Re: Variables not displaying in DEBUG

Needless to say, none of this is needed. You should rarely if ever make age a table field. It defies logic. Age is an ever-changing value and as such, in most cases should be used as a calc field negating the need and all these troubles you had to go through to simply update it.

I say in most cases, since in the unlikely case that you might be designing a database for a funeral home, a Mortician, an Embalmer or the Department of Highways Division of Road Kills, then it would make sense to have it as a table field. Otherwise, I'd keep it as a calc field that will always self-update.

[MikeC]

Re: Variables not displaying in DEBUG

Age makes perfect sense to have as a table field if it is something that won't be changed normally I feel and as such is not such a rarity.

Such as the age at which a person, object, animal, etc. had done something, had something happen, etc..

Age of a something say in a photo...age of a person when at an event or a place...

So I don't think it to be all that unusual to want such a field...nor is it such an unusual circumstance.

And yes, it could be a calculated field...but just as well could be a table field in many cases in which it would not ever be changed...along with the "death" situations mentioned.

[Gary Kissinger]

Re: Variables not displaying in DEBUG

The application of this script is for a database of students that change class as of their birthday. This way I can update all ages in the database before running a class report. I tried using a field rule, but that only works when you add a new record. I thought this was the easiest way to refresh all the ages from a form...

[Gary Kissinger]

Re: Variables not displaying in DEBUG

I forgot to mention - this has to run daily and especially on Mondays...

[G Gabriel]

Re: Variables not displaying in DEBUG

I tried using a field rule, but that only works when you add a new record

Not field rules.

If you are running a daily report, in the report create a calc field:
Student_age=age(Date_of_Birth)

Then filter the report based on the calc field.
You wouldn't need the script.
Nothing wrong with the script except:
a-You are doing alpha's work, and
b-You are doing it twice.

[Gary Kissinger]

Re: Variables not displaying in DEBUG

ok - Thanks for the tip...