Question : Personnel Database with historical information using Infopath/Access

I'm trying to build a personnel database using MS Access and InfoPath as a front end. I'm very comfortable with InfoPath and intermediate level when it comes to MS Access. My question is the following: What is the best way to design tables in Access to maintain historical data for when following changes occur:

Job titles
Job status with begin and end dates
Units
Office

Would you advice to avoid InfoPath as front -end data entry and search form and sticking to MS. Access all together? I find InfoPath much better to work with/program when it comes to building forms. But I'm afraid, InfoPath my cripple some of the functionalities of MS Access (such as memo fields---but I dont need memo fields in this database)

Answer : Personnel Database with historical information using Infopath/Access

I would strongly advise using SQL rather than Access, even if it is SQL Express.  If you are going to have multiple users and use this across the enterprise Access is not really suited.

As far as tables I always use effective dating.  so on all tables, jobs, personnel, org, benefits, certifications, locations, accounts, etc put a starting and ending date.  That way you can leave historical and even future data in our tables and just look for today > startdate and today < endate when looking up records.

I have made some great HR solutions with InfoPath but SQL will be easier to work with (web services) and perform much better down the road.  Most company's personnel records would swamp an Access DB pretty quickly.

Checkout www.infopathdev.com and www.qdabra.com as resources.