COMBO Logic Obsolete?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Under Office 2003 Access, I have an older database that has a form that does
not perform under Vista as it does on my XP system.

I have an un-indexed, two field Table with the first field being a 3
character code and a second field being a description:

Wood Types
Type Description
BEE Beechnut
BOX Box Elder
BUC Buckeye
BUT Butternut

Formerly when I went to my wood inventory form, I would click on the combo
drop down arrow to display the wood types, click on the appropriate line and
the code would be entered on the form. Pertinent properties of the COMO
field are

Control Source Type
Input mask
Row Source Type Tablw/Querry
Row Source SELECT DISTINCTROW [Wood Types].Type, [Wood Types].Description
FROM [Wood Types];
Bound Column 1
Format >
Column Count 2

When the Form is used, the drop down logic displays two columns with only
the Description data and the code is no longer inserted into the COMBO Box.

It appears that this usage of the COMBO box is to simple to place in any of
my reference books. I would appreciate a solution. TIA justphilip
 
Hi,

I'm not sure it will help but "Type" and "Description" is a reserved word in
Access.
Try to rename these to something else.
Under Office 2003 Access, I have an older database that has a form that does
not perform under Vista as it does on my XP system.

I have an un-indexed, two field Table with the first field being a 3
character code and a second field being a description:

Wood Types
Type Description
BEE Beechnut
BOX Box Elder
BUC Buckeye
BUT Butternut

Formerly when I went to my wood inventory form, I would click on the combo
drop down arrow to display the wood types, click on the appropriate line and
the code would be entered on the form. Pertinent properties of the COMO
field are

Control Source Type
Input mask
Row Source Type Tablw/Querry
Row Source SELECT DISTINCTROW [Wood Types].Type, [Wood Types].Description
FROM [Wood Types];
Bound Column 1
Format >
Column Count 2

When the Form is used, the drop down logic displays two columns with only
the Description data and the code is no longer inserted into the COMBO Box.

It appears that this usage of the COMBO box is to simple to place in any of
my reference books. I would appreciate a solution. TIA justphilip
Click to expand...
 
Thanks for the reply. What I find strange is that the only apparent
differences between my old PC and new is the operating system XP vs VISTA. I
have another Table and combo box that is acting the same as the one described
here.

AccessVandal via AccessMonster.com said:
Hi,

I'm not sure it will help but "Type" and "Description" is a reserved word in
Access.
Try to rename these to something else.
Under Office 2003 Access, I have an older database that has a form that does
not perform under Vista as it does on my XP system.

I have an un-indexed, two field Table with the first field being a 3
character code and a second field being a description:

Wood Types
Type Description
BEE Beechnut
BOX Box Elder
BUC Buckeye
BUT Butternut

Formerly when I went to my wood inventory form, I would click on the combo
drop down arrow to display the wood types, click on the appropriate line and
the code would be entered on the form. Pertinent properties of the COMO
field are

Control Source Type
Input mask
Row Source Type Tablw/Querry
Row Source SELECT DISTINCTROW [Wood Types].Type, [Wood Types].Description
FROM [Wood Types];
Bound Column 1
Format >
Column Count 2

When the Form is used, the drop down logic displays two columns with only
the Description data and the code is no longer inserted into the COMBO Box.

It appears that this usage of the COMBO box is to simple to place in any of
my reference books. I would appreciate a solution. TIA justphilip
Click to expand...
Click to expand...
 
There is Little, if any reason for this not to work.

I would first disabled track autoname correct

I would also check the combo box in design mode -- on the "other" tab, turn
off allow auto correct.

I would also do a compact and repair..and also ensure your code compiles...
 
Hi,

There were many issues between A2003 and A2007. Some complaint that the MDB
crash while using A2007. Some had to convert it to ACCDB.

Here's one from Allen Browne;

http://allenbrowne.com/Access2007.html

Try to remove the Name AutoCorrect as Albert suggested.
 
After verifying that this data base works perfectly on my XP/A2003 PC, I just
recopied to my Vista/A2003 PC. Same error occurs! What is there about Vista
that would cause this problem? Should I redirect this question to the Vista
Help Board? TIA justphilip
 
I'm guessing that while you're running Access 2003 on both machines, that on
the first machine you have Access with SP2 installed, while on the new,
misbehaving machine Access 2003 has the latest service pack, SP3 intsalled.
This "upgrade" is filled with bugs, one of which has columns in comboboxes
disappearing! Sound familiar? The culprit is that the vanishing fileds have
something set in their Format property, usually the simple > symbol to
force uppercase. The work around, until Micro$oft gets in gear and issues a
patch, is to remove the formatting.
 
Thank you Ling Adams
I removed the > symbol from the Format definition in the Table and the
problem disappeared. I left it in the Properties Format line of the Form. I
now need to assess the impact of lower case data in theses data fields. Do
you know if there is a notification mechanism for when this fix is made
available? TIA
 
Note using > for the format does *not* change the case of the underlying
(stored) data, only the *displayed* case. So if you didn't have a problem
with it before, you won't have a problem now either.

Pieter
 
Back
Top