Search results

Indeed it does but it spanks the User as well with that annoying message unless you of course add Response = acDataErrContinue into the Not In List event.. If however, you want to be more subtle and keep he User in bewilderment then destroying the keystroke as Wazz has suggested is the way to go. .

In short....Yes. For your Combo Boxes and List Boxes you can use the same method but in the Row Source property rather than the Record Source property which the Combox and List Boxes do not have. You also want to make sure that the Columns are going to be set up properly according to your...

This is actually two items which can be implemented into a single Form. What you need is a Entry/Edit interface with a search mechanism. When it comes to the interface, well, it's all a matter of how you want to present your data for entry or edit. There are so many ways this can be done. In...

Bottom line.....everything you want to do can be done. The thing is...it's not so easy to explain everything you want within a single post. Solve one problem at a time. Pick the first one you want to tackle .

I personally always (well...not always) dynamically create a SELECT query in code for this sort of thing: Me.MyFormName.RecordSource = "SELECT * FROM MyTableName WHERE [MyTableDateField] " & _ "BETWEEN #" & Me.MyFormsStartDateTextBox & "# AND #" & _...

It will look like a Datasheet if you are basing your SubForm from a Table Or Query when using the SubForm Wizard. Create a new Form. If you use the Form Wizard then based the Record Source from your Table or Query. Open the new Form in Design View. Place Labels into the Form Header which...

First off..... The code I provided already takes care of that. As for your date format...force the User to enter the Format you want by setting a Input Mask. Copy and Paste the following line into the Input Mask property for the Date of Query Text Box on Form: 00\ /\ >LLL\ /\ 0000;0;_ You...

In the Form's OnUnload event change the line: If CheckControls = True Then Cancel = True: Exit Sub To this: If CheckControls = True Then Cancel = True Exit Sub Else DoCmd.SetWarnings False DoCmd.RunCommand acCmdUndo DoCmd.SetWarnings True End If .

The Best person to ask is in fact the person the created it. As you know (or may not know) ajetrumpet is a regular participant within this very Forum. Bottom line though, the Sub Form is a Sub Form of the Main Form In DataSheet View with no Master and Child Links between the SubForm and the...

Use a SubForm in Continuous Form mode. You can make it look just like a report if you like. .

Your Message Box was set a little to early in Code. It was displaying before the record is actually saved to Table. Code stops running where a Message Box is displayed until the Message Box is closed. This works but if there was an error after the Message Box then basically....the Message Box...

The answer to both your questions is.....Yes you can. The code below is the same code I provided earlier (with correctons of course) and it also included additional code so as to attempt to do just that. Keep in mind that I can not test this code withoutyou DB or a sample of it. The Code I...

My apologies :o I placed A Exit For statement in the wrong location where it checks Option Groups. I moved it up one line into the If/Then procedure. This was preventing the Function from checking all the other controls once it reached the first Option Group. A problem still persisted. The...

There is something very odd about your Database. A For/Next loop in one procedure outputs to little and a For/Next loop in another procedure outputs to much. For some reason, I think the no matter what loop mechanism we use it's going to be different. Does the Modified Sample DB I sent back to...

Use the Microsoft Access SwitchBoard Manager. Menu: Tools | Database Utilities | SwitchBoard Manager Play with it. You will see how easy it can be.

My apologies...my browser must be acting goofy. The only bold line I see you r post is: This next bit is the section that gets highlighted in my debugger as being wrong.. I've never see the editor light up an entire section of code like that. In any case...based off the Error, I would say...

That's right beanbeanbean, Bob hit it on the nail. The line: For Each Control In Me.Controls should be: For Each Ctrl In Me.Controls and for the: DmCmd.SetWarnings = False Well...there should be no equals ( = ) sign: DmCmd.SetWarnings False Air code....what can I say other than I...

OK...so you want to keep it simple. Well, for duplicating a record, MS-Access can't make it any easier. Just place a new Command button on the Form when in Design View then allow the button wizard do it for you under Record Operations | Duplicate Record. Based on this principle I have...

It would be extremely helpful to know what the Error actually is and exactly what line (or statement) is highlighted. .

As Ken said, you could do a function to remove instances of these unwanted characters. I quickly whipped a simple one up for you. The Function is named ReplaceEx. Just copy and past the following into a Database Code Module: Public Function ReplaceEx(ByVal SourceStrg As String, ByVal...