Replies

If the Company Name is also a field in this table, an easy way is to click in the Company Name field on a form which is based on the Customer table, then click the Find tool on the toolbar. The resulting recordset will be all the customer records with that Company Name. You can use the navigation buttons at the bottom of the form to move between all the records that meet this Company Name criteria.

One way to do it would be to make the Cust_Num dropdown unbound, setting it’s row source property to:

SELECT YourTable.Cust_Num FROM YourTable WHERE YourTable.Route_Num = [Forms]![YourForm]![name of Route_Num dropdown];

This will give you only the Customer Numbers whose Route Number is the same as the Route Number on the form. Depending on the contents of this table, you may have to use DISTINCTROW.

I am familiar with the screen you are referring to Charlotte, but when I looked there, that screen does not seem to display when I am importing an Access table. It only displays when I am importing other file types. What am I missing? … I’d like to learn this.

I do not know how to accomplish this with the Import Wizard, but … If you position in your external Db and write an append query, you will have the option of appending that data to a table in your existing Db. The append window has a radio button that reads Another Database and has a textbox for the complete filename (include the path).

Maybe I am misunderstanding you, but the width of the textbox in the design view does not need to accomodate the entire length of the source statement, only the width required for the data to print on the report. So, try decreasing the width of the textbox in the design view, so that it prints on the report properly, but doesn’t exceed the page width.
Then, of course, there is the obvious solution of moving it somewhere else on the page. If the page is 8.5″x 11″ wide – can’t it fit somewhere else?

I don’t understand why you are using a sub with the expression =Forms![frmStartup]![strDateRange], when it seems that the textboxes on the form are named Starttxt and Stoptxt. Have you tried putting a textbox on the report with the source as =”For The Period ” & Forms![frmStartup]![Starttxt] & ” To ” & Forms![frmStartup]![Stoptxt]?

Sounds like you have placed the code on the OnOpen Event property. Have you tried placing DoCmd.Maximize on the OnActivate Event property for the form as well? I believe the Activate event occurs when a form receives the focus and becomes the active window.

Open the form in the design view and activate the property sheet. Set the Timer Interval property to 5000. This is the equivalent of five seconds and you can adjust the number as you like. Select the On Timer property and click the Build button to open the Code builder. The line of code you need to execute the Close action is: DoCmd.Close. Compile the module. Close the module window and save the form.

There are a few ways to do this, but without additional information … if you link the tables in a query, then all the fields in both tables will be available for calculations. You can either create those calculations in the query or objects based upon that query.

I have not done this, but there is a Weekday function that returns a whole number containing the day of the week. vbMonday = 2
Might testing with that be useful?

When I need to do this, I use VB. I can hold the current record values in variables and then use .MovePrevious to collect the previous values, like this …

‘collect values from current record
vTruck = rsFuel![Truck]
vDriver = rsFuel![Driver]
vDate = rsFuel![Date]
vOdometer = rsFuel![Odometer]

‘collect values from previous record
rsFuel.MovePrevious
vPrevTruck = rsFuel![Truck]
vPrevDriver = rsFuel![Driver]
vPrevDate = rsFuel![Date]
vPrevOdometer = rsFuel![Odometer]

Now, I have the values from both records and can perform the calculation.

There may certainly be a more efficient way to accomplish this, but this has worked for me.

I am accustomed to getting the results you desire by placing the criteria as unbound text boxes on a dialog form.

You can find this is Help under criteria, reports, then Use a form to enter report criteria. This method has always worked for me.

Maybe someone else has used the method you are describing …

The SetWarnings (Action for a macro or Method for a VB module) will accomplish this. For details, both are listed in the Help Index.

I’m not clear on what you are trying to accomplish, but generally … the option group control allows you to choose only one option per group. Since you want to choose more than one, you need to add more than one option group or you can use individual checkboxes or radio buttons, (which are also located on the toolbox), which ever makes sense for your purposes.

Attach the following to the Before Update Event of the form:

If Me.Dirty Then
Me![RefDate] = Date
End If

The Dirty property determines whether the current record has been modified since it was last saved.