Access 2010 Web Databases and the dreaded Lookup field.

[mvanella]

So I have heard it said by numerous people here and elsewhere that lookups are evil and are possibly worse than Satan himself. So with that said, from my new experiences with Access 2010 Web databases, they essentially force you to use them. Is there any way around this while still maintaining the ability to publish the database to sharepoint as well as to restrict the user to specific input for those fields that would otherwise have been lookup?

For example one of the main tables in my database is RMA, which tracks information on repairs. So we have the following

RMA

• Customer
• End User
• Repair Status
• Warranty Period

So each of those fields has a table associated with the data to which I want to constrain the user. What is the appropriate solution for a 2010 Web Database?

 

[boblarson]

With web databases you do have to use them directly in the table. You are right to be confused. The advice is to totally keep them out of tables but now with this newer web stuff, you are, as you say, forced to do so. So, go ahead.