RE: [Axapta-Knowledge-Village] Refresh problem again

[James Flavell]

Title: Message

I am on SP2 but I thought sometime ago I tested on SP4 and it was also happening but I would have to retry that Thanks James   -----Original Message----- From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Harry Deshpande Sent: 15 December 2005 22:10 To: Axapta-Knowledge-Village@yahoogroups.com Subject: RE: [Axapta-Knowledge-Village] Refresh problem again Hi James   “Start position – First” cannot result into this behavior.   Which system are u using? I tried this in V3S3 but cannot replicate the behavior. (though I vaguely remember encountering this long time back)   Regards   Harry     This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm" The code provided (if any) may be written from the point of view of a third party and the programming style/development standards may suit such a point of view.       From: Axapta-Knowledge-Village@yahoogroups.com [mailto:Axapta-Knowledge-Village@yahoogroups.com] On Behalf Of James Flavell Sent: 14 December 2005 10:40 To: Axapta-Knowledge-Village@yahoogroups.com Subject: [Axapta-Knowledge-Village] Refresh problem again   Hi everyone,   I have run into another 'refresh' problem during SO and PO postings.   It seems on the update screen where the user can edit the lines to be updated, that once the  user change the 'recv now' qty and press the key to go to the next line the system goes to the next line AND THEN JUMPS TO THE VERY TOP LINE!!!  This is driving the users mad as they have alot of lines.   I have had a look and can see the datasource "PurchParmLine" is set to 'Start Postiion" = FIRST so this explains why it jumps back to the top record but I do not seem to be able to trap where it is thinking it needs to do a refresh to cause this jump.  Can someone help me with where to stick a break point or even better how to stop this behaviour (i.e. the cursor should just go to the next record) before the users kill me out of frustration ;)   I am using Ax3.0 SP2 but believe I tested it on SP4 with the smae results Thanks James   Sharing the knowledge on Axapta. YAHOO! GROUPS LINKS  Visit your group "Axapta-Knowledge-Village" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.