Search results for query: beforeupdate tags

@Pat Hartman - Great Explanations!!! I wasn't sure if the data macros went in the BE or the FE. I saw JDraw's example database and liked how it worked, but it (obviously) wasn't a split database. I think you had mentioned this approach before, but I had never used it. I checked and I like that...

Where is the "hitting head" emoji when you need it? I know that English isn't your native language but that isn't what I said. What I said was FOR A FORM - the Form's BeforUpdate event is the last event that runs before a record is saved. I didn't say anything about what validation the...

No, in the discussion above, the Data Macro was created on the BE (you can't create on on the link, only on the physical table - so that means in the BE but the function it called was defined in the FE. If you want to use a function in the Data Macro, you MUST define the function in the BE...

@Pat Hartman - You are too kind with the code sample. Thanks again. I don't think I explained that well. Right now all users can edit all fields. Let's call my current users Group A. The new users who will only have access to a few fields would be group B. What I meant is I don't have to tag...

If you only tag a few fields. all the other fields can be changed unimpeded unless they are always locked. UNLESS you prevent it by cancelling the form's BeforeUpdate event, Access saves all changed controls. Here are three useful functions that you can modify to suit your situation. Two of...

It would be nice not to have to tag so many things on my forms, especially if I need to make changes to the forms in the future.

You can lock the controls using a function as suggested above. I can post a more sophisticated version that lets you have controls that are always locked or always unlocked and you only have to tag those two types. You don't need to tag all controls that you want to lock which becomes a pain...

Well, using the "form's BeforeUpdate" solution certainly does that. You didn't ask but here's my version of the lock/unlock procedure. You ONLY need to tag the controls which will be "different". i.e. always locked or always unlocked. All controls which will toggle, don't need to be tagged...

I get your idea and I knew instinctively that your "solution" was flawed. I tried to convey that there are ways to do this that do not involve buttons. As I said, YOU decided what the solution was. You chose to not describe the problem. You started this thread KNOWING what your solution was...

I must be missing something. I am trying to call this function from the form's before update event and I am able to make changes to the information in the fields that are supposed to be locked.

We do know you are not an expert. But, you are performing a technical job and you should endeavor to do it the way a professional would do it. You have a fiduciary responsibility to your employer to ensure the best data you can provide. Otherwise, you should decline and let your employer hire...

I'm thinking the problem is not with the Replace but with the item I'm trying to replace. Let me try to be more specific... Starting with a form I scan a barcode into txtBarcode which has a control source of Barcode (a field in tblPackout). The barcode scanner sends the the data (with it's...

Thanks its working now....

The problem is the code in the close button. For now, remove all the code except DoCmd.Close acForm, Me.Name When you close the form, Access will automatically run the form's BeforeUpdate event. After you get this working, we can help you to add code to get around an error caused by closing...

Logically, I don't see an issue but in Access, the most efficient way to refer to form controls is with the Me. reference. So: If Me.TXTLV = "CML" And Me.txtfrom >= Me.TXTDSAN Then MsgBox "Commuted Leave can't be presanctioned, Please check!!!!", vbOKOnly + vbCritical, "Hello !! Information...

I added a new button to the form to show you how to take advantage of Access and work with its collections and to properly use arrays. Here's the copy code for those who don't want to open the db. To indicate which fields to copy, add a numeric value between 1 and 255 to the tag property of the...

you need to add code to the Form's BeforeUpdate to Cancel if there are some blank fields. it is best to use Tag property of the control, so only those with tags are actually checked. adding a button (and code on the button) on your form will not prevent it from saving the record. you need to...

Is it possible to have a Customer who does not have a phone? Perhaps this is not a realistic criteria. You can check for a value in the BeforeUpdate event. You can set the control's Tag property to "Required", and issue a message as appropriate. BUT it seems reasonable that a Customer may not...

Most people dislike being constrained. Therefore, I do not constrain them by stopping them from leaving controls except under rare circumstances as I said earlier and I do it by using the BeforeUpdate event. You especially don't want to annoy people who didn't actually modify a control so I...

That is what programmers do:) If we knew all the rules we'd need in 2030, we'd add them now but although being an optimist is a prerequisite for the job, we are not omniscient. We do what we can to ensure data entered is rational. For example, ALL dates are validated to some extent but the...