Recent content by SforSoftware

Set in the Form's properties Modal=True and Popup=True, and you should be able to open it in Normal mode.

Pseudo code: If Me.RecordCount = 0 Then If MsgBox("Nothing found! Create new item?", vbYesNo) = vbYes Then Me.allownew = True docmd.gotorecord accmdgotonew End If End If

Don't use the OutputTo method, but use Automation to create a new file from a template. Then open a recordset and use CopyFromRecordset to put the data into your Excel document.

Shouldn't you try to replace: Me!XrayDataOriginalCDQuerySubform.Form.RecordSource = "Select * From XrayDataOriginalCD Where [CaseNumber] = " & """ & selID & """ Application.ExportXML acExportQuery, "XrayDataOriginalCDQuery", "file path here" & [CaseNumber] & ".xml" by Application.ExportXML...

In the After-parameter you use 'wb.range', shouldn't that be 'wb.sheets(...).range' ?

Does this help? DoCmd.Save acModule, "Module1"

maybe this document could help you? http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnoffpro01/html/OfftheChartAccess.asp

Did you try a refresh/recalc at the form? Or try to re-connect the recordset to the form?

Thanx Ken!! Problem seems to be solved by deleting two calculated fields with dlookup's grtz, Bert

thanx, i'll give it a try... (and come back with the results!)

Private Sub cmdButton_Click() On Error GoTo ProcErr If MsgBox(You are about to delete a line. Do you really want to do this?", vbYesNo + vbCritical + vbDefaultButton2, "Warning") = vbYes Then DoCmd.SetWarnings False DoCmd.RunCommand acCmdDeleteRecord DoCmd.SetWarnings True End...

Private Sub Knop0_Click() DoCmd.OpenModule "Form_Form2" End Sub

it are all custom msgboxes, called from macro's or vba.

ok, I tried the 'doevents', but that didn't help anything. Then I tried an 'screen.activeform.refresh'. That seems to solve the problem, but that gives problems with validation in beforeupdate-events (the value is saved by the refresh method). the behaviour of the recalc-method is the same as...

Importing parts of the application is a way to locate the problem, indeed. but the app is very larche so i'd think that'll take more than a week... (also because the problem occurs 'randomized', so it's not easy to reproduce. Yes, I did (both front-end and back-end) and that results in the same...