No, it will always be two people.. It's called the four eyes principle..I made the two columns extra for that. What I'm asking is for a solution to this problem.. I'm open to ideas
I tried it on form_current() but it didn't work.. Actually instead of looking in the table I wanted it to just take what was in the text.value as default for next time
Form_current()
If not isnull(me.txtdate.value) then
Me.txtdate.defaultvalue = me.txtdate.value
End if
A user of my form would like a default date appearing in a text field of the form. This default is to be the last date used on that field.. Is it possible to store this date in the default property. I realise the user would need to save the application at that point, in order for it to remain..I...
Well, to answer your question, with regards to the approval. I have two columns "1_Val" and "2_Val". When the 1st person edits something, his pers_ID is entered into column 1_Val, then with the help of the form, I can see which dataset has something in 1_Val, so that when I show that and I want...
And when in practice - please tell me if this makes sense - I will have the two tables in a centralised Access DB alone( called it Base), with the main access dB, with the forms, linked to base via linked tables.. So that multiple people can use the mdb with a " first come, first save" functionality
What's a relationship window?
It's two tables...Both have the two columns in it. The first table is to make sure the dataset is only coming to the 2nd table (master copy) if it has been validated by two people altogether. What would tend to happen is that the first person corrected or enters...
Ok, I'll try and explain why I'm trying to stop the auto save functionality, you can tell me a better way of architecture..
With regards to the "four eyes principle", a user is to save a dataset with his username in a column "First", then another user comes to save, and it saves the same...
Sorry guys to bother you with this pesky topic. I tried setting the cancel= true in form_before_update(), that gave me another problem where I set " frm.dirty = false", which is necessary before executing SQLs.. So I'm stuck on what to do.. The video you guys posted is interesting, but I'm just...
Yeah thanks.. This video seems to really tackle the subject.
I thought I was done with a cancel=true in the before_update() , but then it doesn't even open the form now.
Ok, I seem to have a simple solution:
In before_update() I set cancel= true. That works.. The only thing is, I need to surpress the message "you can not save this dataset currently... Do you still want to close the database object (yes /no)" , when I close the form.. Any ideas how to surpress...
Hm..I need a bit of help with the architecture. It's bound so that the information comes straight away from the table, but when I want to save, I need to add a flag to a column.
So with regards to this, is it better to make it unbound, and have the text fields and combos update it self...
Hi,
I have a bounded Form with a tab and several text fields and combo boxes.
Now, I only want it to save my input into the fields, when I press the save button, and I can set and check a few things along the way. It seems like it, because it's bound, it saves it anyway. How can I control this?
First of all, thanks for all the information!
I'm left with a very confused frame of mind now however.
Let me maybe elaborate on what I want to do, because there seems to be a few paths, where I'm confused as to which path to go on, especially after reading "lock down database objects".
I have...