<div>
Thanks heaps for your help. &nbsp;Sorry, I should've looked in the online help instead of blindly Googling!
</div>


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

<div>
By the way, I was not advocating you add a timestamp column. &nbsp;I was just parroting what MS had to say on the subject. &nbsp;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.
</div>


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.

<div>
<div class="content wysiwyg-content">
Hello Experts<br />
I am assisting a colleague in upgrading a MS Access 2003 backend to SQL Server 2005. &nbsp;The database front-end will still be an Access 2003 mdb and they will be using ODBC links to the SQL Server backend. &nbsp; &nbsp;<br />
<br />
I have been reading conflicting information about timestamp fields (which I believe the upsizing wizing automatically creates) &nbsp;Some sources say that a timestamp field is required in each SQL table as it makes it easier for Access to update data. &nbsp;Other sources say they are useless and can be deleted.<br />
<br />
Could someone please tell me if there should be a timestamp field in every table on the SQL Server when using a mdb frontend?<br />
<br />
Thanks for looking at my question.<br />
<br />
<br />

</div>
</div>


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.




Upsizing Access 2003 to SQL Server 2005 and timestamp fields

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.

Microsoft SQL Server

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.