Search results

Gilberto, You don't talk about the underlying queries or tables for your form, so I'm making some wild guesses. The error message you report sounds like you're trying to create a record in the recordsource table or query of the subform but there is no relationship yet established between the...

Paul, I've had similar mysterious happenings with the OnCurrent event. As I recall my problems finally resolved when I realized that changing stuff on my form kicked off other events which I was not expecting. I wonder if your problem might go away if you tried to insert your header-specific...

I have wrestled with this problem a lot. Others have, too. See http://www.discontents.com.au/find_aids/makefa_4_1.htm, and note the observation at the bottom of the page. If your reports are not too complex you might consider reading the results directly out of the underlying query, and...

You could try something like this. Suppose your table is "tblReadings", it's primary key is an autonumber field called "ID", and it contains another field called "Meter" containing the meter reading: SELECT IIf([ID]=1,0,[Meter]-DLookUp("Meter","tblReadings","ID=" & ([ID]-1))) AS Diff FROM...

Look at CDO Messaging on the MS Developer Network site. If you can get it to work it's great. If you have Outlook you can access Outlook programmatically. Look at MSDN for Outlook APplication. Warning: The notorious OutLook 2000 Security Patch will seriously get in the way, with lots of warning...

Bob, If I understand your problem, how about defining a small (one field, one row) table, and using it as the unbound form's recordsource. The list box could be tied to the table's field. Whenever the form is closed, the month would be saved in the table. When the form is reopened the...

Sounds like you need to do things to a couple of different tables based on the values and conditions in your opened form. To add a record to a table in the current database you can do something like strSQL = "INSERT INTO tblOtherTable (Field1, Field2) VALUES ('" & [tbxValue1] & "', '" &...

You say you "register" the name and time when the user visits the database (DB). Assuming this means you enter the name and time into a table in your DB. If this is a correct assumption, you could have code similar to the following executed when you want to open one or the other of the forms...

The problem may be in the DLookup syntax- I think there's a missing double-quote. Try =DLookup("[Period]","Period Calendar Table","[Date]=" & Forms![Downtime Entry Form]!Date) If it still fails you might have to take the form's [Date] field and convert it to a date value using something like...

Would an InputBox work to acquire the search name?

Has anyone found success and happiness in using CDO for Win 2000 to send email? Apparently this is MS's new! improved! way to fire off email from your apps. I copied some code off the MS site at...

Does the 3rd field have a default value? With Date the only field on the form, if you just open the form, then close it, you don't create a new record. Check out the Dirty property. In the OnClose event for your form put in MsgBox Me.Dirty to see whether the record has been changed. For...

Before you do the search, be sure the focus is in the form's control that's tied to the field you're searching. That is, if you are expecting the user's search string to be found in the EquipName field of the Equipment table, and the form has a text box named tbxEquipName with this field as...

If the table has an autoincrement-type index ("StockID") you could use DMax("StockID","StockTable") to find the index of the last-stored record. This might be iffy if more than one used is adding stuff to the table - the DMAX could pick up the record added by someone who added a record right...

Think of the DLookup function as a simple SQL query of the form SELECT [StockPrice] FROM StockTable WHERE [StockID] = 37; The third argument of the DLookup function is the WHERE clause of the SQL statement. You probably want to say something like =DLookup("[StockPrice]","StockTable"...

Have a peek at http://www.mvps.org/access/api/api0001.htm Suitably tweaked, this ought to do what you want.

Suggest you look at Access's online help. Search for "updatable". There arre any number of things that can cause a query to become not updatable, and it sounds like you inadvertently implemented one of them. Not very helpful, I guess. Jim

Couldn't you use a combo box with a rowsource of the valid platenumbers? That way the user wouldn't be able to enter an incorrect plate number.

I think you are being MUCH too good to your users! ;-) You could set up a form containing 15 text boxes, with the label = something descriptive about the entry field, and the text box meant to hold an (optional) integer, the order of entry fields on the data entry form. The recordsource for...

Here's what I did in a similar application: 1. Make the top-level cmb (I call'em cbo's) have a rowsource query that lists the mfgrs. 2. Make the hinge series cbo work from a query that lists ALL hinge series WHERE mfgr = me.cboMfgr 3. Make the height cbo work from a query that lists ALL...