My Assistant
|
|
May 2 2011, 04:03 AM
Post
#1
|
|
|
UtterAccess Ruler Posts: 2,197 From: Den Bosch - Netherlands |
Hi!
This only applies for one end user, the rest of the users experience no problems: She uses a MSAccess FE connected with MYSQL through connector 3.51.27. When I try to alter a record (I've tried this at table level) and the current_timestamp field is Null, I can't alter it. It just locks me in the field. On another record where that field isn't Null, I can edit without problems. As everyone uses the same FE and database, and the connector flags are set the same (allow reconnect and return matching rows), there must be a local problem. What can cause this??? |
|
|
|
![]() |
May 3 2011, 03:20 AM
Post
#2
|
|
|
UtterAccess Ruler Posts: 2,197 From: Den Bosch - Netherlands |
I'm sorry to bump this thread, but I still can't figure out what is wrong. It now seems that two PC's are having this problem (using other accounts doesn't matter), the rest is ok.
I've checked ODBC versions, ODBC flags and regional settings, but nothing! Also Access settings don't vary as far as I can see... |
|
|
|
May 3 2011, 05:34 AM
Post
#3
|
|
|
UtterAccess Ruler Posts: 2,197 From: Den Bosch - Netherlands |
Well, sort of fixed it by giving all the empty timestamp fields a bogey value... but I still don't know what the problem was.
|
|
|
|
May 3 2011, 07:37 AM
Post
#4
|
|
|
UtterAccess VIP Posts: 5,508 From: Brixton, front line |
What is the Create Table statement for your table?
d |
|
|
|
May 5 2011, 05:13 AM
Post
#5
|
|
|
UtterAccess Ruler Posts: 2,197 From: Den Bosch - Netherlands |
I don't know, that table was created a long time ago... Or is it possible to recreate that statement??
To make it clear, the table wasn't altered either for quite a while, so the cause of this problem lies somewhere else... |
|
|
|
May 5 2011, 05:31 AM
Post
#6
|
|
|
UtterAccess VIP Posts: 5,508 From: Brixton, front line |
Hi MrSiezen,
You can enter the SQL command: SHOW CREATE TABLE YourTableName; But, as you say, if it used to work then perhaps it's not the problem. Yet again, it might yield a clue! Have you upgraded the server recently? Maybe something in a new version is breaking what used to work? d |
|
|
|
![]() ![]() |
|
Go to Top · Lo-Fi Version | Time is now: 19th June 2013 - 04:32 AM |