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 |
|---|---|---|---|---|---|---|
| MOHAMMED ARFAN | 11/21/09 | 7 | 4 | 8 | 10 | thanks |
| John | 11/20/09 | 10 | 10 | 10 | 10 | From your reply, I need to clear ..... |
| Ashley | 11/20/09 | 10 | 10 | 10 | 10 | Thanks for all your help I had ..... |
| Jamie | 11/19/09 | 10 | 10 | 10 | 10 | |
| Steven | 11/18/09 | 10 | 10 | 10 | 10 | Ah! That's simple. I should have thought ..... |
=Format(Date() + Choose(Weekday(Date(),vbMonday),1,1,1,1,3,2,1),"dddd") To test this Substiture a Date value for Date(). For example: Format(#11/20/09#+Choose(Weekday(#11/20/09#,vbMonday),1,1,1
First, you need to understand how Access stores DateTime values. Access stores date/time values as a double precision number where the integer portion is the number of days since 12/30/1899 and the decimal
If I follow you, you have two tables in one to many relationship. What's not clear is which is the one and which is the many. But these tables should NOT have the same primary key. They should both have
I would not use a combo in this case. I would use either an Option Group or a Check box. But the process is the same no matter what control you use. In the After Uodate event of the Status control
Depends on the structure of your database. The proper structure would be using three tables like this: tblPayroll PayrollID (Primary Key Autonumber) EmployeeID (Foreign Key PayDate PayPeriodStart
Answers by Expert:

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