Search results

And just in building on Pat's reply, i.e. 'the accde is not an executable...' we're trying to help you find where to go to make the file an accde file...but, as Pat said, it won't be an exe file! Exe files are basically executable on any machine...while running an accde file requires some...

Two more questions (Please only answer once! 😊) If you go into Design Mode then switch and run the Form, do the buttons work? If you close the Form completely...then open it by clicking on it in the Navigation Pane on the left, do the buttons work? Linq ;0>

Don't run v2019, so can't say! But question: Does any code on the errant Form work? Linq ;0)>

While this type of error is usually associated with the opening a Form, it apparently can be caused by all kinds of things, and, to the best of my knowledge, it is very seldom, if ever, actually connected with communicating with a OLE server or ActiveX Control! The most common cause, going by...

A true photo-finish! All bettors should retain their tickets while the track stewards review the photos!:cool:

There really is no VBA in general! VBA is actually a group of languages...VBA for Access is different than VBA for Excel. And to make matters worse...Access has many Properties and Functions with the same names as Properties and Functions in Excel...but they often perform different tasks and...

Exactly! So by adding the If Me.Dirty Then Me.Dirty = False before the DoCmd.Close you force the Save...and if required data is missing...it'll be caught. Linq ;0)>

Perhaps in the past @zeroaccess has been using the Command Button Wizard or the code DoCmd.Close to close his forms. In pre-2007 Access, if you used the wizard or the above code to close forms...'required fields' unpopulated were simply ignored and the form would close, dumping the errant...

Q. And what happens if the user never enters the Control at all? A. NOTHING! The validation code never fires! Linq ;0)>

Short Date is how the field is formatted...not the DataType...as HTC asked! In the underlying Table is it defined as a DateTime Datatype?

Placing it in the Control's BeforeUpdate event is useless! All the user has to do, in order to make your validation useless...is to simply not enter the Amounts Control! If the Control is never entered...none of its events are executed! Validation for determining if a Control is populated...

Right...like they've fixed the age old bug where using the aforementioned SendKeys turns off the Numlock key! Don't think I'll hold my breath. Linq ;0)>

Assuming that your intent is to have first item entered as Line# 1 second as Line# 2 etc. you must be doing something in the background to cause this...and I don't think we can help you with seeing your file...as sorting can be done in VBA code, Macros, or in the Property Pane...and we'd really...

Yes...anytime one Control's appearance, Value, etc. depends on some state of another Control, you really need to do your checking/validation in the Form_BeforeUpdate event. The reason is simple...You, as the developer, have no way to know in what order your end user will enter data! The Form's...

Actually...Me.FieldName works for me, in v2007, for a Field in the underlying table but not bound to a Control on the form. Or did I misunderstand the question? Linq ;0)>

Micron is right...we have to see the exact code (Sub headers included) that you're using! I was also wondering, given your aim with this code, why you wanted to pop a warning if the Units_Recived were = Units_Ordered? Another late thought...are the Fields connected to Units_Recived and...

I tend to do this kind of thing, when two or more Controls are involved, in the Form_BeforeUpdate event...doing it in a Control's BeforeUpdate event is dependent on the user entering data in a certain order (i.e. Units_Ordered entered before Units_Recived, in this example) and in my experience...

Try this (untested) Private Sub Form_Open(Cancel As Integer) Me.TimerInterval = 1 End Sub Private Sub Form_Timer() Me.TimerInterval = 0 'Run proceedure here End Sub Linq ;0)> Sorry...day late (well 4 minutes) and a dollar short!

Actually you can set the Column Order in Form View! I've had situations where two different orders were required...and simply triggered the change using the Double-Click event of two of the columns. Here's an interesting article called "You Can Do That With Datasheets?"...

I agree with theDBguy...this looks like a custom designed Form...not a Form with this kind of border. Do all/other Forms have a pink border? If so, this may be the result of a Theme being used. Did you design the Form...or did you inherit it from someone else? Linq ;0)>