parentform.mark_record() fetches next record

[Hal Epting]

I have an invoicing application that I after the invoice is filled out the user pushes a button that starts the final process to print the invoice etc.

The xbasic script I'm using in the "on push" button to begin the process is:

'Saves & marks current record
parentform.commit()
parentform.mark_record()

'Save calc'ed fields to Database
DIM tbl as p
tbl=table.open("invoice_header")
tbl.fetch_first()
tbl.change_begin()
tbl.Total_Parts=Calc->Parts
tbl.Total_Labor=Calc->Labor
tbl.Total_Parts_Labor=Calc->Total
tbl.Total_Amt_Disc=Calc->Amt_disc
tbl.Total_Amt_Tax=Calc->Amt_Tax
tbl.Grand_Total=Calc->Grand_Total
tbl.change_end(.t.)

'To change to the checkout form
rec = table.current().recno()
fp = form.view( "checkout" )
fp.index_set( "" )
fp.find( rec )
fp.index_set( "cus_id" )

This code works fine for 3 or 4 invoices and then say on the 4th invoice, you push the button and rather than staying on the current invoice, it moves to the next invoice. I've played with the code and if I take out the parentform.mark_record() all is well. I Any help will be greatly appreciated...

[whanigsberg]

RE: parentform.mark_record() fetches next record

Hal:

The form the button is on (parentform) is based on which table or set? The invoice set?

Is this the same form as the checkout form mentioned later? I guess no.

"...you push the button and rather than staying on the current invoice, it moves to the next invoice." In the previous sentence, to which form does "it" refer? At what point in the code does it change focus?

Bill

[Hal Epting]

RE: parentform.mark_record() fetches next record

Bill:

The form the button is on (parentform) is based on the invoice set. The checkout form is seperate from the invoice form.

When I push the button, as the checkout form gets focus, you can watch the record change on the invoice form to the next record. It appears after the .mark_record(), is when it changes to the next invoice. "The checkout form pops up on top of the invoice window" (see attached .jpg)

If I close the checkout form and fetch the record that I was invoicing, it has been marked() as I wanted.

I appreciate your help.

Hal

[Mick Magnuson]

RE: parentform.mark_record() fetches next record

Hi Hal
I am by no means an expert with scripts, but have learned some ways to get them work the way I want. Since you say the invoice record is changing after the mark, how about getting the recno right after the commit, then do the mark, then fetch with the recno variable to get the record back to the one you want. Then open the checkout form. If your invoice form is indexed by something other than recno, you can also pass the key data to a variable and find by that that instead of recno. Just a thought.

Mick

[Tom Cone Jr]

RE: parentform.mark_record() fetches next record

Hal,

I don't think parentform.mark_record() advances the record pointer.

1) if it did, your script would skip the second invoice each time, right?

2) I built a simple model here. Put a button on the form that did this:

parentform.commit()
parentform.mark_record()

Added an embedded browse to the same form. When the button was pushed the current record is marked, but the record pointer does not advance to the next record.


Is it possible you have not shown us the entire script your button push runs?

-- tom

[Hal Epting]

RE: parentform.mark_record() fetches next record

Tom:

I've checked the script of my button against my original post to ensure I didn't miss anything, I've posted everything.

When the Checkout form fires, I do not have any further scripts run until I push the "complete invoicing" button.

"...I don't think parentform.mark_record() advances the record pointer. 1) if it did, your script would skip the second invoice each time, right?..."

I played with the invoicing system to check the number of records it's skipping, I put six in and only record #2 was skipped? However, if I take out the parentform.mark_record() and attempt to invoice that same record #2, it allowed me to do it?

I do appreciate your help

-Hal

[Hal Epting]

RE: parentform.mark_record() fetches next record

Hi Mick:

I'am fairly new to scripts and not quite clear on your reply. I'll have to open the books here and do some research to try and follow what you suggested.

"... how about getting the recno right after the commit..." Could you give me an example of how this is done?

"..then do the mark, then fetch with the recno variable to get the record back to the one you want..."
Again, not clear on where I should go with this.


Thanks,

-Hal

[Mick Magnuson]

RE: parentform.mark_record() fetches next record

Hi Hal

Something like this

parent.commit()
dim global rec as n
tbl=table.current()
rec=tbl.recno()
parent.mark_record()
:this.index_set("")
tbl.fetch_find(rec)
parentform.resynch()

'goes to the rest of the script transferring the calc fields, etc.

If you don't want to keep the record number as the primary sort you can add another :this.index_set("your index") to the bottom of it.

Mick

[Tom Cone Jr]

RE: parentform.mark_record() fetches next record

Hal, the interaction of events in your field rules, and the two forms, and the various buttons is complex. Best way to get to the bottom is to post a working example, using dummy data if your data is sensitive. Why not zip the database and post it here, with a text file explaining which forms and buttons are involved?

-- tom

[Tom Cone Jr]

RE: parentform.mark_record() fetches next record

Hal, another idea.

Check out the redim command. If your script is running multiple times in a row, you probably want to redim the variables, instead of just dimming them. I think redim is the only way to re-initialize a variable in this kind of situation.

Don't know if this will help, but thought I'd mention it.

-- tom

[Hal Epting]

RE: parentform.mark_record() fetches next record

Tom:

"...the interaction of events in your field rules,
and the two forms, and the various buttons is complex.
Best way to get to the bottom is to post a working example,
using dummy data if your data is sensitive. Why not zip the
database and post it here, with a text file explaining which
forms and buttons are involved?..."

Here it is, I hope we can find an answer... They usually are staring us in the face and were too blind to see it!!

From within the Estimating/Invoice form, I have a few examples of data. If you click on it brings up the Checkout form. As I've explained in my previous posts, several invoices will mark() the record properly and then all of the sudden it skips a record??

It always seems to be the second one in the database...

As an example, bring up record #2, ANYONE, LISA and press on the button. The Checkout form pops up but notice the record on the invoice screen will change to YOURNAME, FIRSTNAME.

Now close the Checkout form and go back to the ANYONE, LISA record. You can see that it has been marked().
[for testing purposes I put Unmark Record button on the screen so I could unmark the record being tested without completing the invoicing process.]

Now, in the xbasic code in the Print invoice Button if you remove the second line: parentform.mark_record(), record #2 now stays on the form as it should??

Again- Appreciate the help from everyone...

-Hal

[Hal Epting]

RE: parentform.mark_record() fetches next record

Well, I thought I sent the sample file but I see now the system allows a max of a 1.0 meg file. The file I attempted to send was 1.9 meg. I'll see if I can get the working model down to these requirements tomarrow morning...

-Hal