Recent content by ptpaton

Great. So they provide a product that works on only simple databases, and if any complexity is present in the code at all, it crashes. Way to go, Microsoft. Should have known better than to believe MS would put out a "free product". -Patrick Nine times out of ten, the simplest solution is...

I'm having the same problem. I've determined so far that as soon as any VBA code runs, the error appears. Error trapping doesn't help at all, either. I'm researching the problem also. -Patrick Nine times out of ten, the simplest solution is the best one.

Kermit, you are a trouble maker! j/k :) -Patrick Nine times out of ten, the simplest solution is the best one.

Glad to help Kermit! -Patrick Nine times out of ten, the simplest solution is the best one.

Try Me.[tblCoilTracking subform].Form!CTDate Also, make sure that CTDate and DRDate are the actual field names? If the text boxes and the field names are the same, you can also run into problems. Name the fields one thing, and add txt to the start of the name for the control names. So CTDate...

Aximboy, You can run queries to maniuplate data on the subform, and then perform requeries, but it's really better to get into VBA to starting updating subforms. What specifically are you looking to do? -Patrick Nine times out of ten, the simplest solution is the best one.

Kermit, In design view of the mail form, select View>Code. Make sure the only code you've entered is OnUpdate of the date field on the mail form. Then, make sure there's no code running on the sub form by designing the sub form and selecting view code. If that's not it, try formatting the...

Ahhhh. I see, then lupin is correct. If you want to see the other field, add another text box bound to that field? Otherwise you have to combine the fields in the builder as lupin suggested. -Patrick Nine times out of ten, the simplest solution is the best one.

I've been developing for 10 years now, and here's how it breaks down: 90% is self taught from experimenting, trial and error, resolving error codes, and digging through MS help. 5% is from google and awesome boards like this one. 5% is outright theviery from you good people. Thank goodness...

Whoa...hang on Brogrim. ZmrAbdulla is correct, you can have as many columns in the combo box visible as you'd like, once you drop down on it. Make sure you have 2 or 3 in the number of columns, the column widths are appropriately wide enough, and the size of list is big enough to accomodate...

Kraeg, What I would do is put a command button on the form. OnClick of the button, you can do a couple of things. 1. You can create a simple select query that's limited to your form's recordset and export it using the DoCmd.TransferText command or 2. You can create a recordset, set it to...

A subform is usually imbedded in a main form, and opens with the main form, so I'm not really sure what you're trying to do, but you could open the form as a dialog or normal form with any of the action properties of the combo box. Have you thought about something like DoCmd.OpenForm on the...

StarScream I think there are two issues you need to think about: 1. If you want multiple records to appear on one form you need either continuous forms or you can base a list box on a table, and set the record source equal to tblYourTabl!Note That will give you a list of all the notes. 2. To...

If possible, always save data in a table unformatted. It's best to format only where the end user sees the data. In a blank column in your query, type this into the field box. Date: Format([DateField],"mm/dd/yy") This will format your datefield to short date. -Patrick Nine times out of...

Format(DateField,"mm/dd/yyyy") -Patrick Nine times out of ten, the simplest solution is the best one.