You are here:
I can answer almost all types of questions relating to Microsoft Access usage and application design. My strengths are database and interface design.
I've been designing databases for over 15 years working with dBase, FoxPro, Approach and Access.
Author of Microsoft Office Access 2007 VBA
Techncial Editor for Special Edition Using Microsoft Access 2007 and Access 2007 Forms, Reports & Queries From Que Publishing
| User | Date | K | C | T | P | Comments |
|---|---|---|---|---|---|---|
| Hashim | 11/07/09 | 10 | 10 | 10 | 10 | I got what I wanted from your ..... |
| Dave | 11/07/09 | 10 | 10 | 10 | 10 | Thanks. I was afraid that was the ..... |
| Gabi | 11/06/09 | 10 | 10 | 10 | 10 | thanks |
| Christina | 11/06/09 | 10 | 10 | 10 | 10 | It does thank you |
| Christina | 11/06/09 | 10 | 10 | 10 | 10 | Thank you for your input. I appreciate ..... |
You still are making this clear. what you are saying doesn't sound logical. If you are saying that the Register Date may be the same as the Actual Date and when it us you don't want to key in the same
First, your database is not normalized properly. By having fields for each division number you have created a repeating group which violates normalization rules. You should have 2 tables here. One
Access 2007 has two modes for displaying documents (forms, reports, queries, etc.); Tabbed documents or Overlapping Windows. These modes are set using the Office button, selecting Current Database and
Very good. You referred to a document number, so I assumed it was a number datatype. I still think the second method I suggested will be easier for the users. Hope this helps, Scott<> Microsoft
I suggest you read up on Normalization. Customer name should exist in ONE table and ONE table only, the Customer table. The customer table should have a primary key (not name) that would be used as a Foreign
Answers by Expert:

©2009 About.com, a part of The New York Times Company. All rights reserved.