[Combobox].boundcontrol <> 1? 1

[lameid]

Somewhere along the way I picked up the idea that a combo/list box should always have it's bound column set 1 because sometimes I saw unusual behavior like storing the first column even if some other column was specified. Worst of all my recollection is that it was intermittent. It would work fine and then all of a sudden it would change behavior to something bad. Am I just remembering an old defunct bug that doesn't exist anymore (possibly from Acc97)?

I have a reason to specify a different column in Access 2010 (minimizing Stored Procs in SQL, bad FK in one table) and I couldn't find anything quickly on the issue I am remembering...
My test worked but my recollection is intrmittent problems (rather it worked and then all of a sudden would break and normally would stay broken despite my efforts).

So two questions:

What versions have people not had problems with bound column <> 1 / what versions have you had problems with?

Is this a bug that was fixed and if so what version / patch level?

 

[dhookom]

I don't recall any issues that weren't PEBKAC. However my memory isn't all that reliable ;-)

Duane
Hook'D on Access
MS Access MVP

 

[lameid]

I have been able to easily avoid the possibility for many years.
I remember (vaguely) seeing it often enough to believe it wasn't the code. So if it was not me, maybe someone else monkeyed with the data directy... That makes me want to use a 4 letter word... Us*r

(for anyone having a bad day * = e)


Anyway, if it is not in recent memory as an issue, then I think I am safe in 2010.