Data entry form reversing data fields in table

[awscorp]

I've not seen this happen before in this DB that has been used for years here.

In the table on the left you can see the Year and Place fields with the information they contain, and on the right in the Data Entry form the first user returns properly but the next person shows the Year and Place data reversed.


So if I enter a new record at this point the form will enter the Year into the Place and the Place into the Year field in the DB.


Wondering if anyone has come across an issue like this before..
Thanks..

[June7]

Something is changing the RowSource property of comboboxes?

If you want to provide db for analysis, we might be able to figure out what.

Why is VoteYear not a date/time field?

[Micron]

Or the bound column property of the combos has been altered? Check that the bound column is correct.

[awscorp]

Feels like it is but doesn't do it for all records.. This is in the Datasheet form entry mode so it seems like if it were going to reverse fields then it would want to do that with all the records but it seems to feel random for some reason.

The year wasn't a date field since they had only been a number but then they started doing them more than once a year so it ended up being just a text field, that they use the default value for so they really only needed to enter a place.Voters - Reversing table fields example .zip

[awscorp]

Forgot to mention this can be seen when using the 3rd option in the menu list labeled with "Datasheet".

Hoping I am just missing something simple here..

[davegri]

Unable to replicate. Added users and ballots.

[awscorp]

Thanks for trying it. From here if I create a new person then go to Datasheet
1. after entering a new record I close and reopen the datasheet view
2. click the drop down of Place and can see the default year appear
3. then after selecting a place my default Year disappears and the previously entered record reverses.

I can't think of how I can be doing anything different from here. Does feel like something about the data entry form is getting mixed up on the fly.

[moke123]

Looking through your code I noticed you do not have option explicit declared in your modules. You also disable warnings in your macros but do not re-enable them.

I also could not recreate your issue.

[awscorp]

Thanks for taking a look at this.. I will update those macros\modules for sure.

[awscorp]

One thing I am noticing is that when in the datasheet view if I click the plus on one record then it doesn't matter which record I click next and they get revered (Left side). But if I click on the plus and then click it again to collapse before clicking on a second one then it doesn't seem to reverse on me. (Right side)
Actually I forgot to include I did click on the record before clicking the plus in this, which is what caused me to see the fields swap places. Not sure if that might mean something?

[davegri]

I have never seen that behavior before.
But perhaps the reason is because I've never seen datasheets used that way before.
Pretty rare user technique, I think.
For me, the reversal (when it occasionally happened) in the form did not update the table in that reversed way.

Quite odd and the form has no module code.

Some more experimenting and found that if I made these changes, the problem went away, but can't say for sure if it fixed it because the problem is very intermittent.

[June7]

Also cannot replicate issue.

Why does Property Sheet display in Datasheet View?

I have never used datasheet/subdatasheet view, only form/subform.

[awscorp]

Thanks for taking a look at this! I can certainly have them test it out. This was created 20 years ago so my guess is that because it didn't require any coding and it was in an easy to navigate view for them to search\enter data they never tried anything different. I had been thinking about overhauling all of it but they are so used to it and I didn't want to make it more complicated.. lol..

[awscorp]

Just an update on this issue, in case anyone was curious. This seemed to only happen with the Office365 version of the application version 2410\2411, but if I loaded Office 2021 instead then the issue did not happen. So after a couple of months with Microsoft support they did determine the issue and will have a fix for that behavior in the 2510 version due to be released at some point soon. Thanks for everyone who took a look at this. It was definitely a strange issue..