Search results

The point isn't to prevent physically changing the Control's Value. The point is that the Control is populated the first time a second Control has data entered...but if that second Control is later edited, the original Control's Value doesn't change.

That would assume that the entire Record was entered when the Record was first initiated...which is not always the case. Users sometimes stop mid-Record to visit the loo...go to lunch... (gasp) take a smoke! Linq ;0)>

Still having trouble following you...my fault, no coffee yet...but if I read you correctly...once Me.BookingRef is populated...you want it to remain at that Value...even if other value(s) change? Try checking to see if it's already populated...and only do the data assignment if it's empty: If...

Don't have time to experiment, right now (sorry) but you're correct...the Locked and Enabled Properties only apply to physically interacting with a Control...and don't apply when populating a Control via code, as you're doing. But to be honest, it's hard to understand why if the Control's Value...

First off...you're not going to get a message when you 'move the focus from 1 field to the other...' You'll get a message, if appropriate, when you go to Save the Record. You could only get a message when moving from Control to Control, by calling a Procedure of the Control...such as the...

The Form's purpose, whether to Edit a Record or to add a new Record, makes no difference...your code still needs to be in the Form_BeforeUpdate event, just like before! Linq ;0)>

Glad we could help! Linq ;0)>

There are a number of ways to approach this, such as Private Sub Form_BeforeUpdate(Cancel As Integer) If Nz(Me.Control1,"") = "" Then MsgBox "Control1 Must Not Be Left Blank!" Cancel = True Control1.SetFocus Exit Sub End If If Nz(Me.Control2, "") = "" Then MsgBox "Control2 Must Not Be...

First off...I'm pretty sure you can't use the Like operator with a Numeric datatype...such as GaugeNum. And despite DoCmd.SetOrderBy being used in Microsoft help sites... Typing in DoCmd.setorderby, and moving off of the line, it doesn't become DoCmd.SetOrderBy, as it should. Nor will...

Truth be, a lot of us do the same thing. In addition to easily doing data manipulation within a Query...it adds a second layer of protection, a sort of buffer, between the user and the Table...always a good thing! Linq ;0)>

Current problem aside...you absolutely must have a copy of the Front End on each user's PC. Having multiple users sharing a single Front End, on a network drive, is the sure way to repeated episodes of corruption, speed and timing problems, and all manner of strange, odd and curious behavior...

And your original post said nothing about where you need it to go! As the Mailman said, it needs to go wherever you need it to go. Perhaps a plain language explanation of exactly what you're trying to do would help us to help you. Linq ;0)>

This kind of this has worked for me for years: Private Sub Form_Error(DataErr As Integer, Response As Integer) If DataErr = 2113 Then 'Data entered does not match datatype of Control Source If Screen.ActiveControl.Name = "YourNumericField" Then Response = MsgBox("Data For This Field...

Building on @pisorsisaac@gmail.co's comment: http://rogersaccessblog.blogspot.co.uk/2010/12/should-i-use-compact-on-close-feature.html Pay particular attention to Roger's fourth point! Paradoxically, as he pointed out, compacting is a recognized cause of corruption and should only be done...

Having multiple users sharing a single, non-split database, sitting on a network drive is, as has been said, a sure way to repeated episodes of corruption, speed and timing problems, and all manner of strange, odd and curious behavior! Multiple users simply have to work off of a split database...

Which is a good argument for not using Navigation Forms...most experienced developers don't! Much better to 'roll your own' nav form'...where each Form is an independent Form to be opened! Linq ;0)>

Well, the code I gave you will only allow 0-9 and the Minus Sign. Linq ;0)>

The problem with letting the Access Gnomes handle this is that they also consider Decimal Points, Commas and Plus Signs to be 'numeric!' This code will warn users if any characters except 0-9 or the Minus Sign (-) is entered...replacing Value2Test with the actual name of your Control, of...

Just be aware that by doing this, you can only enter new Records...you cannot view/edit previously existing Records. Linq ;0)>