First, I should note that you are responding to a thread that from 7 years ago, with the most recent post nearly 4 years ago.  Second, as far as I...

According to the presenter in Vienna, if you define them as Datetime2 (2) that seems to work without problems.  That gives you 1/100th (10ms) seconds precision.  Hope that helps.

This is a known problem, and there are some workarounds which may or may not be acceptable in your situation.  See the following link for the info.

https://docs.microsoft.com/en-us/office/troubleshoot/access/access-linked-table-deleted

I also am...

I presume our paths have crossed somewhere in the past, but haven't been able to figure out where and when.

First, lets make sure we are talking about the same thing. ...

There are a number of good resources in evaluating your options.  One of my favorites is:

https://www.fmsinc.com/MicrosoftAccess/SQLServerUpsizing/index.html

Others you might consider:

https://support.office.com/en-us/article/Migrate-an-Access-database-to-SQL-Server-7bac0438-498a-4f53-b17b-cc22fc42c979

https://www.techrepublic.com/blog/10-things/10-plus-tips-for-upsizing-an-access-database-to-sql-server/

https://msaccesslinks.com/

I spent 20 years working with SQL Server...

Since several weeks have passed, I hope you have sorted this out.  First of all, it's not clear whether you are using Integrated Security, or Standard Security.  Your question suggests...

The * in that refers to this:

*As of January 14, 2020, Office 365 will no longer be supported on Windows 7 SP1.

A few things to note:

• It is only available as a download from the MS Store - https://www.microsoft.com/en-us/p/access/cfq7ttc0k7q8?activetab=pivot:overviewtab
• Such an installation isn't supported or tested by Microsoft
• You could also...

For some strange reason, the post I made last week seems to have disappeared.  So I shall try again:

I suspect your issue has to do with the primary key on...

One of the most common issues where you get the **#Deleted** message is where you have a boolean (Yes/No) field in the SQL Server table that doesn't have a default...

Sorry for the delay in responding.  And yes, it is essentially the sort of code that William suggested.  It sounds as though you are dealing with a continuous form that...

Are your users getting those kind of ODBC errors from a form where they are adding/editing data on a form?  Or are they adding or editing data at the table...