NetTalk Central

Author Topic: Retain row after changing record?  (Read 5186 times)

Alan Telford

  • Jr. Member
  • **
  • Posts: 81
    • View Profile
Retain row after changing record?
« on: June 18, 2008, 06:35:24 PM »
Is it possible to remember the current ROW on the browse, so that after the user has pressed SAVE on the form, it comes back to the current row.

I have NT4.30, running on a SQL2005 db, with Page-Loaded browse.
It works as long as I change a record on the 1st page.
But ... if I switch to the 2nd page, and change and save a record, then the browse seems to always RESET to the very 1st row.

If I have 3-4 items to change on e.g. the 4th page, then this is VERY SLOW.
Press NEXT 3 times (to get to page 4).
Press CHANGE, to edit the record, then SAVE.
Browse resets to TOP.
Press NEXT 3 times to get back to page 4 ...(etc)...

Alan

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11250
    • View Profile
Re: Retain row after changing record?
« Reply #1 on: June 19, 2008, 07:23:01 AM »
Hi Alan,

It should work as you require already.
What backend are you using?

Cheers
Bruce

Poul

  • Full Member
  • ***
  • Posts: 160
    • View Profile
Re: Retain row after changing record?
« Reply #2 on: June 19, 2008, 07:44:36 AM »
"I have NT4.30, running on a SQL2005 db, with Page-Loaded browse.
It works as long as I change a record on the 1st page"



fwiw, i see the exact same thing, as well, both sql 2000/2005.
the first page works great...

some very simple (2 fields no embeds)

Alan Telford

  • Jr. Member
  • **
  • Posts: 81
    • View Profile
Re: Retain row after changing record?
« Reply #3 on: June 19, 2008, 01:08:46 PM »
I'm using MSSQL 2005 standard edition sp2.
I originally thought it was only when changing records on a CHILD browse.
But in this case, it was a standalone browse.

This is definitely not working for me.

Alan

Alan Telford

  • Jr. Member
  • **
  • Posts: 81
    • View Profile
Re: Retain row after changing record?
« Reply #4 on: June 19, 2008, 05:07:07 PM »
I''ve created a sample application to demonstrate the problem.
It uses the sql 2005 sample database AdventureWorks.
This can be downloaded form http://www.codeplex.com/MSFTDBProdSamples/Release/ProjectReleases.aspx?ReleaseId=4004

This can be used to show two different problems:
1. Run, and choose "Product", then press "next" to go to 2nd page. Edit a record, and then press SAVE. Note that the browse is reset to the 1st item and does not remember the row.

2. Choose "Setup | Form - Tabs", change to the 2nd tab "SubCategory". Now Edit a record and press SAVE. Note that the page is reloaded and switches to the 1st tab.

"AdventureWorks.zip"


[attachment deleted by admin]