more tabs problems -1

[DaveM]

tabs Question. And thanks for any help.

I am editing a record for a person who has made 2 purchases. when I go from a tab to the save button(not on the tab), it backs up one record to another purchase done a year ago. It is duplicated with a customer who maed 3 purchases. It is only backing up to the last name, because the first name is different in one of them.

The save button has several scripts(1 in xbasic) attached, but none have anything to do with this. there are no scripts attached directly to the tabs. If I change the form to not allow navigation, it still changes the record. It ONLY happens with same last names as all other deal data is different.

What could possibly have an influence on this. Maybe me??

I will attach the xbasic to be sure:

'Open the table to update...
dim tbl as p 
tbl = table.open("upsfollow2",FILE_RW_SHARED)
dim target_record as n 
target_record = 1
  
'Find out what the last record in the table is
dim last_rec as n 
'Set the index to record number order
Dim itbl as p 
itbl = tbl.index_primary_put("")
tbl.fetch_last()
last_rec = tbl.recno()
tbl.enter_begin()
tbl.ACCT = a5_eval_expression("=Acct")
tbl.DATEOF = a5_eval_expression("=Date")
tbl.NOTE = "\"New Contact Notes\""
tbl.NEXTDATE = a5_eval_expression("=Date+1")
tbl.enter_end(.t.)

tbl.enter_begin()
tbl.ACCT = a5_eval_expression("=Acct")
tbl.DATEOF = a5_eval_expression("=Date+1")
tbl.NOTE = "\"1st Day Call Back - Send Thank You Letter\""
tbl.NEXTDATE = a5_eval_expression("=Date+2")
tbl.enter_end(.t.)
tbl.enter_begin()
tbl.ACCT = a5_eval_expression("=Acct")
tbl.DATEOF = a5_eval_expression("=Date+2")
tbl.NOTE = "\"2nd Day Call Back - Get appointment\""
tbl.NEXTDATE = a5_eval_expression("=Date+3")
tbl.enter_end(.t.)
tbl.enter_begin()
tbl.ACCT = a5_eval_expression("=Acct")
tbl.DATEOF = a5_eval_expression("=Date+3")
tbl.NOTE = "\"3rd Day Call Back - Get appointment\""
tbl.NEXTDATE = a5_eval_expression("=Date+4")
tbl.enter_end(.t.)
tbl.close()

Thanks all!
Dave

[MoGrace]

Re: more tabs problems -1

Hi Dave,
Have you checked your tab order on the form? If the Save button does not have a tab set or if the tabbed object or Save button is the last object, it can cause this to happen. The cursor expects to go somewhere - although for me it usually goes to the next record not the previous!

[Cheryl Lemire]

Re: more tabs problems -1

Hi Dave,

Look at your form events and any object events. As you know, I use tabbed objects extensively and have never had a record change unless I tell it to somewhere in my code.

The code you provided, is this in your save button? Seems like something is missing if it is, like the commit. I am assuming you are saving the currently edited record first? Then creating several records in the same table with the same acct? Or perhaps the records you are creating are in a separate table.

Either way, personally, I would retrieve the acct value from the record just edited prior to saving it. Then use that value to create the addl records. I am not sure why you would be retrieving the last record in the table? I do not see what purpose that accomplishes?

[MikeC]

Re: more tabs problems -1

Dave,

A stab in the dark...Try

itbl = tbl.index_primary_put[COLOR="Red"]()[/COLOR]

instead of

itbl = tbl.index_primary_put[COLOR="red"]("")[/COLOR]

[DaveM]

Re: more tabs problems -1

Cheryl,

That is in the onsave event of the form. It is the only part I have not fully checked and wondered if someone might see something there. It puts information in a child table as a seperate process. This worked fine witout the tabs, and so did the rest of the form. i have never had a record change in a backward motion. It just threw me.

The good part is that it seems to have corrected itself. All of my tabs have code on the last field to give focus back to a field on the same tab.

I took out the ontab change event to save the record. i do have other triggers to save. When a user hits the save button, which is required to leave the record, it is saved and a couple things happen. It saves a record in the log file(seperate table) of who saved and if changes were made. None of this has to do with record navigation.

right now I am leaving it alone caues it is working.

Dave