Minty
AWF VIP
- Local time
- Today, 00:30
- Joined
- Jul 26, 2013
- Messages
- 10,646
Hi All, I have a strange problem that I sort of know the answer to but wondered if anyone had a sensible workaround;
Azure SQL back end. Simple client table with a number of fields including CreationDate.
CreationDate has a SQL default value of Getdate()
Once a record is created you cannot edit it. If you set a local default date of either Now() or Date() no problem, so it's something to do with the data stored from the Getdate() function.
The value of the date field is somehow locking the record from being edited.
The server data type on the field is good old fashioned Datetime.
Access sees it as a Date/Time data type.
The table has an Identity field set as the primary key.
Has anyone else seen this behaviour, or know how to get around it? I'm baffled.
I'm using the latest ODBC Driver 17 for SQL Server, so don't think it's that.
Azure SQL back end. Simple client table with a number of fields including CreationDate.
CreationDate has a SQL default value of Getdate()
Once a record is created you cannot edit it. If you set a local default date of either Now() or Date() no problem, so it's something to do with the data stored from the Getdate() function.
The value of the date field is somehow locking the record from being edited.
The server data type on the field is good old fashioned Datetime.
Access sees it as a Date/Time data type.
The table has an Identity field set as the primary key.
Has anyone else seen this behaviour, or know how to get around it? I'm baffled.
I'm using the latest ODBC Driver 17 for SQL Server, so don't think it's that.