UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
> Write Conflict - Planning For And Workaround, Access 97    
 
   
dw85745
post Aug 29 2019, 12:30 PM
Post#1



Posts: 112
Joined: 29-September 10
From: AZ


----------------
Background
-----------------
I use Access strictly as a backend.
Currently I have a VB Program that updates certain Access tables (call them data tables) automatically (mainly on time criteria but time varies).
Also part of this VB program are User Forms which modify properties in other Access Tables (call them User tables).

---------------
Question
---------------
My concern are:
1) Will I get a write conflict from Access if on the odd chance the user tries to Update a User tables at the same time the App tries to write a Data Table?
2) IF so what is the best way to handle this conflict ?
a) Where do I find the error codes for Write errors (assume there are more than one)
b) SHould I process those error codes in the calling program and then attempt to rewrite the record
- or-
c) or is it better to somehow deal with that error within Access itself -- and if so , how?
This post has been edited by dw85745: Aug 29 2019, 12:31 PM
Go to the top of the page
 
 
Start new topic
Replies
tina t
post Aug 29 2019, 02:17 PM
Post#2



Posts: 6,290
Joined: 11-November 10
From: SoCal, USA


QUOTE
Also part of this VB program are User Forms which modify properties in other Access Tables (call them User tables).

i can't imagine why anyone would allow users to modify table properties. but regardless of the business need or purpose, changing the structure of any object in a live database, where other users have current access to the db, is a recipe for corruption.

hth
tina

--------------------
"the wheel never stops turning"
Go to the top of the page
 
dw85745
post Aug 29 2019, 03:39 PM
Post#3



Posts: 112
Joined: 29-September 10
From: AZ


--------------
theDBGuy
-------------
Thanks. Haven't had a problem to date, just going over some code and want to make sure.

-----------
tinat
-----------
Hi tinat:

QUOTE
i can't imagine why anyone would allow users to modify table properties

If by your statement you mean modifying the table structure, the answer is No and I agree with you.

If however, you mean changing the value of a table property stored in a table, then I disagree.
Depending on the application, each user may want to customize things for themselves
and those values are stored in Access within a table structure.
Not sure how you would do it, but if you have a better solution -- other than an INI or Flat file, I'm all ears.
This post has been edited by dw85745: Aug 29 2019, 03:44 PM
Go to the top of the page
 
tina t
post Aug 29 2019, 07:31 PM
Post#4



Posts: 6,290
Joined: 11-November 10
From: SoCal, USA


storing data is storing data, hon, it doesn't matter what use you're going to put it to. if your users are adding/editing/deleting data in tables, no problem - that's what tables are for. if that data is going to be used to temporarily set various interface properties at runtime, AFAIK that's not a problem, either.

setting object properties and then saving those property settings in the object - that's altering structure. bad idea for a production db, especially a backend db that is shared by other users. altering structure should only be done by the developer, on the development copy of the db.

i think you already got what i said above, and we're on the same page. just restating it for folks, especially newbies, who may read this thread going forward. :)

hth
tina

--------------------
"the wheel never stops turning"
Go to the top of the page
 

Posts in this topic



Custom Search


RSSSearch   Top   Lo-Fi    22nd January 2020 - 02:32 AM