xbasic: enter date

[vasant panjabi]

trying to enter a date on the onpush button event.

on a print button on a form have the following:-
(form properties: change record ticked (not permitted)

tbl = table.current()
tbl.change_begin(.T.)
PRINTED_INVOICE_DATE.VALUE = date()

nothing happens..the print invoice field is blank as ever & if pushed 2nd time - get an error: 8005.

hwr, if change form properties to allow changes with :
PRINTED_INVOICE_DATE.VALUE = date()
works fine

what am i doing wrong & how to i make this hasppen with the
form properties set to `not permitted`.

as usual any help most appreciated.

v.p

[forskare]

RE: xbasic: enter date

I understand you are tyring to print a form and when you push the print button, you want the current date to print on the form?

If so, why not simply display the current date on the form all the time, since the field is already there? You can drag / drop the system date from the Drag/Drop list or put date()in the OnArrive event for the date field. I'm sure there are other ways but that's a quick thought.

kenn

[Peter.Wayne]

RE: xbasic: enter date

try

parent.restrict_change=.f.
PRINTED_INVOICE_DATE.VALUE = date()
printed_invoice.refresh()
parent.restrict_change=.t.

[vasant panjabi]

RE: xbasic: enter date

thank you doctor - that worked perfectly.

thanks again

v.p

[vasant panjabi]

RE: xbasic: enter date

dear ken,

printing a report - and the date is to keep a record -
when the invoice was printed.

thks,
v.p

[CALocklin]

RE: xbasic: enter date

To clarify this to help you avoid the same problem in the future:

tbl = table.current()
tbl.change_begin(.T.)
PRINTED_INVOICE_DATE.VALUE = date()

The problem here is that you are mixing methods and you can't do that. The first two lines are working in the table mode. To complete it in the table mode, you would have to use:

tbl = table.current()
tbl.change_begin(.T.)
tbl.printed_invoice_date = date()
tbl.change_end()

Then add:
parentform.resynch()
to get the current form up-to-date with the changes to the table.

HOWEVER, IF the *form* is already in the change mode and you run a parentform.resynch, the data will probably be saved and the form may even jump to another record. This is a good reason NOT to mix modes!

The format of the third line in your original script:
PRINTED_INVOICE_DATE.VALUE = date()
is using a reference to the field box on the form itself.

That's a little like saying you went home and put the garage door key into the lock on the front door to get in. After all, they are both doors to the same house so it shouldn't matter which key you use. (Yeah, in many houses the back door key and the front door key are the same but this is usually not true of the garage door itself.) The same thing is true here. The data in the form originally came from the table and will eventually be saved in the table but, in the meantime, the data on the form is NOT the data in the table.

Maybe a better example is a fax. The information on the fax I send to someone else is originally the same as the information on my original copy of the fax but it isn't the same piece of paper. It's entirely possible (in fact, quite common) for the recipient to pencil in some changes (like a signature) and return the fax to the original sender. So, the fax that's in the hands of the recipient is a little like the form on your screen - it isn't the original. You can either change the original or change the copy and then send it back.

I hope this helps make sense out of what's happening.

Cal