Search results

Are you trying to create something like a Tree View?

Not to speak for Mark but I believe he was suggesting that you use a control (like a text box) on your form to either display the message, or to be a trigger for the message box. So txtFirst is a hypothetical text box on your form. Personally, I'm not sure why you need any of this. You said in...

tblReminders needs to be in quotation marks within the DLookup; TxtFirst = nz(DLookup("ReminderDate", "tblReminders", asWhere), "NONE FOUND")

The simple answer to your question is yes, that is the purpose of forms. The reason your Crocodile form is only allowing entry of new records is because you have the Data Entry property set to Yes. Correct that and you will be able to view/edit existing records as well as add new records...

Unfortunately no (afaik). OWA is browser based so standard Office automation code won't work. Any interaction would need to be through a browser object model. You would need to do some research on browser automation through VBA.

What did you try? Did you add a text box control to the main form and use it as the Master link source for your second subform?

Looks like you got your solution in your other thread

Use the crosstab as the record source of a form or report and total the columns in the footer

See this link for a method.

You might look into what Stephen Lebans has here, a collection of customized list box functionality.

You can accomplish this with two queries. First you will need a Totals query that sums the Amount by Invoice for each Division in descending order. You need to leave the ID field out of this query in order to sum correctly. SQL would look like the following (correct for your actual table/field...

"it keeps bugging" is rather vague. Are you referencing the subform control properly? The subform control is the "window" that holds the subform. It may, or may not, have the same name as the subform itself, depending on how you added it to the main form. Is Tbl_Category the correct name for the...

You could use something like the following (aircode); Dim strWhere As String If Nz(Me.Combo1, vbNullString) <> vbNullString Then strWhere = strWhere & "([Field1]=""" & Me.Combo1 & """) And " End If If Nz(Me.Text2, vbNullString) <> vbNullString Then strWhere = strWhere &...

Aircode (untested) and this does not include the code modifications that others have suggested so you'll have to adjust for that as well. Private Sub cmdImport_FileName_Click() On Error GoTo Err_Handler_1 Dim folderspec As String Dim fs, f, f1, fc, s Dim rs As DAO.Recordset Dim...

Can you upload a small database with some sample data that demonstrates the problem so I can see what you've got going on?

If you need to see records in the Site table that have no related record in Compensation then you would just reverse the logic of the query; SELECT SiteID FROM Site LEFT JOIN Compensation ON Site.SiteID = Compensation.CompSiteID WHERE Compensation.CompSiteID Is Null

I thought that's what you wanted Again, what you seem to be asking for here sounds the same as what you said it returned in the first quote above. I'm not really clear on what results you are expecting.

You would use a query like the following; SELECT CompSiteID FROM Compensation LEFT JOIN Site ON Compensation.CompSiteID = Site.SiteID WHERE Site.SiteID Is Null

If this is a one to many relationship, and Compensation is the parent table, why are you storing SiteID in Compensation to begin with? Can you elaborate a bit more on your table structure?

You seem to be indicating that the only reason you split the db is because you were selling someone a copy, which leads me wonder about your understanding of the reasons for splitting a database. What does this mean? What problems are you encountering after you split? What steps are you taking...