Records jumping

[Hilllo]

Me again-

When the sales department are trying to enter notes in a record, it suddenly jumps to a record near the end and the data is put in the wrong account. I tried to duplicate it and I can't, but I did watch a lady do it. I looked on the postings, but they seem to be about saving records.

Alpha is locally installed on all machines and they access the database from the server. They have the latest patch.
They run Windows XP.

The record jumps if they hit "enter" to begin to type or if they are hold shift to put in a capital letter.

Thank you-

Lori

[Daniel Weiss]

check if you any "on_key()" events or any other events on the from which could cause the problem

[Hilllo]

records jumping

I did check to see if there were any events, but there isn't any.
Database is Modeless.

Anything else I can look for?

Lori

[Bill Parker]

1. do a database compact.

2. rebuild indexes for the table(s)

3. Open the table/set in the default form and see if the problem occurs there.

4. you mentioned notes. if you have a memo field do this in the interactive window
t = table.open("person")
vResults = t.memo_check("v")
t.close()
?vResults

substitute your table name for 'person'.

If there are memo errors, check the documentation for memo_check(). there is an option to repair.

5. are there any field rule events? best if you can remove them for testing.

Bill.

[Raymond Lyons]

First, please see the top item in Forum Support so everyone will know who you are.

Assuming you are dealing with a set and the �notes� is a memo field, I was kind of hoping someone would have the ultimate solution to this problem because I have seen it too. Tracking it down is very difficult because I could never reproduce it on my development machine. It only happened on a multiuser network environment.

For what it is worth my only solution so far has been to

1. Implement a version of Peter Wayne�s �Memos and Browses That Work� at:

http://www.learn alpha.com/MemosThat...osThatWork.htm

2. Additionally, by default I turned off Enter New and Change on the main form and then required the user to press a button to be able to make changes or create a new record. This button turns off form navigation and sets an edit flag that prevents other users from doing anything except to view the record being changed. When the user finishes changing the record he/she must press another button that saves the changes, turns off the edit flag and once again allows navigation on the form. These two buttons appear to the user to be one and the same button with different labels depending on the mode (I did not but one could even do it all in one button).

Now, I wish I had a better way to deal with this problem, but I spent many hours trying to figure out and fix iy. In the end I had to implement the above to prevent a mutiny by my client.

Not sure this helps, but maybe there is some comfort in not being totally alone with the problem. I hope someone else has some insight into a cause allows a less drastic fix.

Ray Lyons

[martinwcole]

check to see if the memo field is the last field in the tab order - if it is, and you enter before you are actually IN the field, you may be just jumping to a new record.

[Jim Chapman]

Hello Lori,

I have seen this a couple of times. Once it was happening because of a couple of event scripts in certain circumstances, were interfering with each other. In a couple of other cases that I've seen, it was involved with sets that were complex, tables recursively linked in multiple times, etc. The most recent situation where I saw this, I could duplicate the issue at will. Simplifying the set structure appeared to cure the problem in version 6 but more telling, moving the database with no change to version 7 solved the issue using the origional set structure. I�d try downloading the version 7 trial and see if that solves the problem.

Good luck,
Jim

[Raymond Lyons]

Hi martin,

That may be the case for whoever Hilllo is but it is not in my case.

Ray

[Elke]

I too have this problem. I have done the same as Ray. I truly hope this is fixed in V7 and will not upgrade unless I am assured that it has. Unable to test as it only happens on a multi-user environment.

[Jim Chapman]

I too have this problem. I have done the same as Ray. I truly hope this is fixed in V7 and will not upgrade unless I am assured that it has. Unable to test as it only happens on a multi-user environment.

Hello Elke,

I can tell you that the latest situation I was involved in, a move to v7 took the problem away. I was able to repeat the problem at will in v6, in v7 it went away. I was using the same database with both versions going back and forth. As I said earlier, I have seen this several times over the last couple of years. Once it was a user coding problem, where two event handlers were interfering with each other. All other times it involved a set structure that was less than optimal. IMHO, there is a esoteric bug in v5-6 that only shows up in certain rare situations where set structures might be an issue. In v6 I was able to watch the code (in the debugger) jumping the record. In v7, didn't happen. So I can say with a certain amount of confidence that IF you are running into the same situation I saw, v7 solves it ........... in that situation ............ :-)

Just my thoughts,
Jim

[Elke]

Thanks Jim, I guess I'll give V7 a try.