By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
431,819 Members | 1,573 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 431,819 IT Pros & Developers. It's quick & easy.

Bug Workaround (Combo Box text converted to number)

P: n/a
I'm trying to make an accessible form for my users but am having a hard time doing so. I've created all tables with normal PKs (Autonumber) and query-generated ReadableIDs as a very intelligible unique ID.

However, when I try to link tables between them (or siphon data using the lookup wizard) my readable ID fields are converted to numbers and are linked to the PK rather than the readable ID.

This is not a huge issue as most times I can work around it. What I simply cannot do is this:

I want to have my combobox list readable values (done), then look up the actual id for those values in their table, then return to the combobox the autonumber id for that specific readable value.

Thanks for your time in advance :)
Nov 23 '10 #1
Share this Question
Share on Google+
3 Replies


ADezii
Expert 5K+
P: 8,628
Adrian, you are going to have to post some specifics, such as: Field Names and Data Types, Row Source for the Combo Box, Table Names and Linking Fields/Types, etc...
Nov 23 '10 #2

P: n/a
to simplify things I have the following setup:

Projects Table: ProjectID As AutoNumber, ProjectReadableID As Text

Timesheet Table: ProjectReadableID as lookup wizard to ProjectReadableID from above, but it actually just takes values from the primary key ProjectID, making it a number

Row source for the combo box has to be Projects.ProjectReadableID or else I just get numbers (which really mean nothing)

My intention is to use ProjectReadableID which is a text field containing client name, project type and date and is used to make selecting a project in the timesheet as easy as possible.

PS: tables are much more complex than what I posted, just simplified them because those are the problem fields.
Nov 23 '10 #3

P: 12
I've solved it!

Complicated thing though.
Nov 24 '10 #4

Post your reply

Sign in to post your reply or Sign up for a free account.