Return from a form to the new record on the browse

[terryd]

Windows7 Ultimate 64bit Clarion8.8778 Nettalk5.44
In previous versions after creating a new record the called browse would display the record just created allowing the user to then add records to a child browse on the same browse screen.
Now the brecord displayed is always the3 first valid record.
Is there a way to ensure that the new record is the selected record?

[terryd]

A point for completeness of information. I have converted the database from tps to MSSQL. I don't see why this could affect it but maybe it has.

[Bruce]

This did change recently, but unfortunately you're now stuck between a rock and a hard place.

The key problem is in identifying "the record that has just been added". So let me preface the rest of my answer by asking you what your Primary Key field is doing. Is it an Auto-number field? Is it set by the server or the client? (ie are you letting MsSql auto-number the field itself?)

cheers
Bruce

[terryd]

Hi Bruce
The primary key field is an autonumber field using the standard primary/unique/autonumber setting from the dictionary. I haven't changed to MSSQL doing the autonumbering.
On the parent form I have set Prime autoinc even if not necessary
What I have done to alleviate the issue is to incorporate the child browse on a tab of the parent form which works fine, the only issue is the the browse that is called still doesn't show the new record on save but the child browse displays the related information even though a different record is highlighted (but I assume not actually selected)

[terryd]

Hi Bruce
Any further information on what I can do.

[Bruce]

Are you really using build 5.44?
I assumed you were on 6 because this change only occurred in 6.
Cheers
Bruce

[terryd]

Yes version 5.44 (see attached)
Additionally since at some stage I will be converting to Version 6 what will I need to look out for that has changed?


[attachment deleted by admin]

[terryd]

Bruce
Additional information
I have the original program using the tps files. When I add a record there the browse called displays the added record.
The tables that the SQL version is accessing have exactly the same keys, indices etc as the original tps files.
It appears that the problem is definitely linked to the sql tables but the normal clarion apps (win32) that were converted and using the same tables have no problem at all.

[Bruce]

Yes, it's definitely related to SQL, and specifically related to the issue of determining "what record was just added". However this was (I think) working in most cases (specifically auto-numbered cases) in NT5. (In NT6 thre's a complication here, that I'm aware of, but that shouldn't be affecting you yet.)

So I think the first step is if you can make an example for me, with MsSql, duplicating the effect. Specifically make sure you get all the auto-numbering settings the same, and also the "advanced tab" settings the same.

I'll run that example through NT5 to see if I can spot the root of the issue, and then also in NT6 to see the effect there.

cheers
Bruce