Update Field to current logged in user ID with new record command button

  • You did start a new post, but not a new thread.  In answer to your most recent question, Access 2013 and 2016 do not support ADP projects, but Access 2010 and 2007 still offer the same ADP support as earlier versions.  However, later versions of SQL Server (2012 and later) are reported as not working with the ADP connection process that 2008 and earlier versions did.  Hope that helps.

    Wendell
    Colorful Colorado
    You can't see the view if you don't climb the mountain!

  • WendellB - Sunday, April 23, 2017 2:39 PM

    You did start a new post, but not a new thread.  In answer to your most recent question, Access 2013 and 2016 do not support ADP projects, but Access 2010 and 2007 still offer the same ADP support as earlier versions.  However, later versions of SQL Server (2012 and later) are reported as not working with the ADP connection process that 2008 and earlier versions did.  Hope that helps.

    Thank you. That is what I thought.

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • We have an Access Project (.adp) running on Access 2003 and have recently moved the database from SQL Server 2008 to 2014.  Not recommending this platform, but have no budget for getting to a more modern and supported platform, and need to get a few more miles on a twenty year old program.

Viewing 3 posts - 31 through 32 (of 32 total)

You must be logged in to reply to this topic. Login to reply