Thanks Duane for the link.
As strange as this sounds while creating and using several large databases I've actually never used forms and rarely ever entered any data manually. How can that be? Nearly all my databases use imports for their main data tables, and the secondary tables once set up often never needed to be changed.
If I understand you/the link correctly, I should create a form for the data entry, and while the form will show the full lookup data (in this case "ABC of XYZ St, 1/01/2013") the table will only store the relevant index data (in this case "1"). Hence the table data is kept as clean and precise as possible. Is that correct?
Finally for what its worth in the actual database the fields are actually Cust_ID, Cust_Name, Job_StartDate etc. I only used the shortened names in my post to make things simpler.
Thanks Again
Sean
--- In AccessDevelopers@yahoogroups.com, Duane Hookom <duanehookom@...> wrote:
>
> Sean,
> It sounds like you are misusing lookup fields. You might want to check out the opinion of most "technically mature" Access MVPs at http://access.mvps.org/access/lookupfields.htm.
> The Cust field in the Jobs table should store the ID value from the Customers table. The Job field in the Payments table should store the ID field from the Jobs table.
> In addition, you might want to consider a naming convention that doesn't allow use of reserved words for field names like "Name" and "Date". I would also use CustomerID, JobID, and PmtID rather than just ID.
> You can use combo boxes in your forms to display whatever columns from your Row Sources that you wish.
> Duane Hookom MVP
> MS Access
>
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (3) |
Please zip all files prior to uploading to Files section.
Tidak ada komentar:
Posting Komentar