Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM ODBC Driver » View Thread |
Messages 1 to 4 of 4 total |
ODBC Link Table Problem with TimeStamp |
Tue, Apr 3 2007 9:52 AM | Permanent Link |
Michael Valverde | I have a DBISAM Tables I am trying to Link from Access 2002 via ODBC Connection.
For most of my tables everything works fine - select, update, delete. I have a few table - the primary ones of my system - that have a TimeStamp field. Those tables keep giving me Write Conflict errors in Access 2002 when I try to update/delete from them. I am on DBISAM 4.22 Build 6 Access 2002 Win Xp SP2 Any ideas? I really don't want to have to quit using the timestamp fields - would require a lot of work! Thank, Mike Valverde Senior Developer ACS Technologies |
Wed, Apr 4 2007 5:25 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Mike,
<< I have a few table - the primary ones of my system - that have a TimeStamp field. >> Could you send me a copy of one of the tables that is giving you problems ? I just tried updating a table with a timestamp column in it using 4.25 B3 and Access 2003 and it works fine. So, either it is something specific with 2002 or it is an issue with the table that I'm using. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Apr 9 2007 3:07 PM | Permanent Link |
Michael Valverde | Tim,
I attached a sample table in Demo.zip. Also, take note that we changed the default extension of the tables to .ACSDAT so Anti-Virus wouldn't mess with us anymore. .DAT is not liked by many AV programs. (Great feature in DBISAM by the way!) I hope its just an issue with Access 2002! Thanks, Mike Valverde "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote: Mike, << I have a few table - the primary ones of my system - that have a TimeStamp field. >> Could you send me a copy of one of the tables that is giving you problems ? I just tried updating a table with a timestamp column in it using 4.25 B3 and Access 2003 and it works fine. So, either it is something specific with 2002 or it is an issue with the table that I'm using. -- Tim Young Elevate Software www.elevatesoft.com Attachments: Demo.zip |
Mon, Apr 9 2007 7:59 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Michael,
<< I attached a sample table in Demo.zip. Also, take note that we changed the default extension of the tables to .ACSDAT so Anti-Virus wouldn't mess with us anymore. .DAT is not liked by many AV programs. (Great feature in DBISAM by the way!) I hope its just an issue with Access 2002! >> Are you using a custom signature with the tables also ? If so, what is it ? Thanks, -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Monday, April 29, 2024 at 05:23 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |