Search results

When you open the DB from the zipped file, the file is actually copied to a temp folder to run and probably can't see where any associated references, paths or files are located. You can create a self-extracting file with the shareware version of winzip. Hope this helps?

Under your conditions , try using "Expression is" instead of "Field Value is".

The only way I can think of would be to output the report to an RTF file. Hope this helps?

You can use the Validation Rule & Validation Text properties of your text box to trap the invalid input.

Possibly a printer problem? (Report was based on a specific printer) or Adobe was installed recently? (Has been known to cause problems with Access)

If you do a search on "Dialog" you should find something, as I think I saw that discussed a month or so ago.

Or you could put the User into a global variable. Or put in a hidden textbox on a form that stays open all of the time, and then check the textbox whenever you need to.

I don't think there is a way to trap within access. Would possibly have to be done at the Windows level, which would affect everything (not just access). The only option I can think of would be to catch it in the OnChange or BeforeUpdate Event of the control.

Don't have 2003 that I can verify on, but I found this on Googgle. (in Tools / Options, View tag, under dual-font support)

Sorry I am using 2000. Don't know if 2003 has that option or not. Will try to find out.

This assumes ID is numeric & ID is the correct field name: Private Sub Form_EditRecord(Cancel As Integer) Dim stLinkCriteria As String stLinkCriteria = "[ID] = " & Me.[YourTextBox] DoCmd.OpenForm "YourFormName", , , stLinkCriteria End Sub If ID is a String: stLinkCriteria =...

DoCmd.OpenForm "frmsend mail" Hope this helps?

Look in Tools, Options, View Tab, Dual Font Support, Use Substitue Font. You can set which font to display when the user doesn't have that particular font loaded on their machine. Hope this helps

Just make sure you split the DB, create MDE from Front-End (FE) and keep the Back-End (BE) as an MDB. Hoope this helps?

It may be less trouble to recreate the query, import everything into a new DB or use an SQL statement.

DoCmd.GoToRecord , , acNewRec

Try this link. http://www.tek-tips.com/faqs.cfm?fid=4289

By chance did you change the name in the table itself also.

DoCmd.OpenReport "Invoice", acViewPreview, , "[Inv_Nr] = 15" Hope this helps?

DoCmd.GoToRecord , , acNewRec Hope this helps?