We help IT Professionals succeed at work.

Upsizing Access 2003 to SQL Server 2005 and timestamp fields

Last Modified: 2012-05-05
Hello Experts
I am assisting a colleague in upgrading a MS Access 2003 backend to SQL Server 2005.  The database front-end will still be an Access 2003 mdb and they will be using ODBC links to the SQL Server backend.    

I have been reading conflicting information about timestamp fields (which I believe the upsizing wizing automatically creates)  Some sources say that a timestamp field is required in each SQL table as it makes it easier for Access to update data.  Other sources say they are useless and can be deleted.

Could someone please tell me if there should be a timestamp field in every table on the SQL Server when using a mdb frontend?

Thanks for looking at my question.

Watch Question

Top Expert 2012
This one is on us!
(Get your first solution completely free - no credit card required)


Thanks heaps for your help.  Sorry, I should've looked in the online help instead of blindly Googling!
Top Expert 2012

By the way, I was not advocating you add a timestamp column.  I was just parroting what MS had to say on the subject.  I have little or no experience linking to MS Access or MS Access for that matter, so I could not say one way or the other.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.