Bad advice there man without slogan, i also gave it here Win32::ODBC insert question, but was corrected.
One thing esolm is doing wrong, and princepawn hinted on(real close) is not using an AutoNumber field. It's Microsoft's answer to autoincrement.
Anyway, why don't you just use MS Access to design your database, then you can get to business

CREATE TABLE sessions (
   SESSION_ID  bigint(20) NOT NULL auto_increment,
   SESSION_DATE    datetime,
   FILE_ARCHIVE    varchar (25),
   constraint pk_session PRIMARY KEY (session_id)
);

or to be MS Access Specific

CREATE TABLE sessions (
   SESSION_ID  bigint(20) NOT NULL AutoNumber,
   SESSION_DATE    datetime,
   FILE_ARCHIVE    varchar (25),
   constraint pk_session PRIMARY KEY (session_id)
);
[download]

btw, here are some MS Acces SQL related links i dug up when I was messing with it 2 months ago:
http://officeupdate.microsoft.com/articlelist/o2kAccessArticles.htm
http://msdn.microsoft.com/library/default.asp?URL=/library/techart/acacclinks.htm
http://support.microsoft.com/support/kb/articles/Q140/6/36.asp
http://support.microsoft.com/support/kb/articles/Q208/6/79.asp
http://msdn.microsoft.com/training/courseware/1539.asp
http://officeupdate.microsoft.com/2000/downloaddetails/sp2upd.htm
http://support.microsoft.com/support/serviceware/access/acc2000/

and some article titles you should google, cause i just saved them to my hd, and don't have the links:

Advanced Microsoft Jet SQL for Access 2000.html
Fundamental Microsoft Jet SQL for Access 2000.html
Intermediate Microsoft Jet SQL for Access 2000.html
Tips and Tricks for Access 2000.html
Fundamentals of Relational Database Design.html
A Simple Guide to Five Normal Forms in Relational Database Theory.html
[download]

 
___crazyinsomniac_______________________________________
Disclaimer: Don't blame. It came from inside the void
perl -e "$q=$_;map({chr unpack qq;H*;,$_}split(q;;,q*H*));print;$q/$q;"