Crazy problem

M

markmarko

Whoa... Occasionally, our users are seeing data in a couple forms change
before their eyes. For example, while on a record for an order from Bill
Smith, they go to change the status of the order, and the data in the name
and address fields changes to another name.

I've personally seen it where the name that pops up ends up inheriting the
original last name! So, by changing a field on one record, it is incorrectly
populating a field on a different record!

I've seen it happen on our Install Orders form. It's a form with about 6
subforms, a number of text boxes.

We have a form we call Order Handler, which has two subforms, one with sales
orders, and the other with matching install orders. So it's possible a user
would have two forms open which are accessing the same tables.

Is this, in itself, enough to cause this problem?
 
A

Allen Browne

1. What version of Access?

2. Is the application split, so each user has a separate copy of the front
end?

3. Is there any code in the events of these forms or their controls?

My first guess is that whoever designed the forms used some event to assign
a value to something else, and that's what is causing the crazy behavior.
 
L

Linq Adams via AccessMonster.com

When Access starts changing from one record to another "without the user
changing them," the first thing that comes to my mind is the "Cycle" Property.
In Design View on the form, try going to

Properties - Other

and change the Cycle Property from "All Records" to "Current Record Only."

and see if that helps.
 
M

markmarko

Sorry for the lack of background info...

1. Access 2007
2. Yes, app is split. be on server, fe auto-updates using Tony Toews updater.
3. Yes, there's lots of code in various control and form events, all of
which I wrote, and none of which should cause this problem

More response under Linq Adams's post below...
 
M

markmarko

Well, the 'crazy' part is that it's not actually going to another record, or
at least it doesn't appear so. SOME of the fields change to show a different
records data, but it's seemingly not just switching to a different record
because alot of the data from the original record remains.

It's intermittent, and I cannot yet determine the cause, so it's difficult
to reproduce to check things like if the primary key on display is changing
(which would tell me if it's actually going to another record or not).
 
M

markmarko

'Should' being the key word here, of course.

The problem only popped up recently, like two days ago, and I haven't
changed the code really with the exception of adding error handling to all
the procedures. But I have written the error handler to not run on my
machine, so I can debug more easily. Error Handling only applies on user
machines. The problem has occurred on my machine so I strongly believe it's
not that codes fault.
 
A

Allen Browne

You could test that by making a copy of the front end, and settting the
HasModule to No for this form and its subforms. Then try to reproduce the
problem.
 
M

markmarko

Ok, a little more info...

It IS going to another record, but the unfortunately part is that whatever
the user had just changed on the first record is getting changed on the
record it changes to!
 
M

markmarko

Ok, so I just discovered that it happens even if the change is made directly
in the underlying table as well. So, that eliminates VBA as the direct cause.
 
R

Rockn

Scroll wheel on the mouse perhaps? I have seen the wheel do some funky
stuff, especially if it is stuck between scrolls and then slips. Does it
happen to every user or a select few users?
 
M

markmarko

No, I didn't have SP1 for Office 2007. I'm downloading it now, thank you...

All users but me are running AccessRuntime2007 (not full version). Would
they benefit from SP1 Office 2007 as well?
 
M

markmarko

Well, turns out I did have that SP1... Must have been a part of a previous
windows update.
 
A

Allen Browne

markmarko said:
No, I didn't have SP1 for Office 2007. I'm downloading it now, thank
you...

All users but me are running AccessRuntime2007 (not full version). Would
they benefit from SP1 Office 2007 as well?

Yes.

Actually, if you create an MDE (ACCDE) in Access 2007 SP1, it won't work in
Access 2007 runtime without SP1.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top