Recent content by wjmontague

I had no problem installing my Front Page 2000 software on my Home Computer but when I try to install it at work it just hangs. The preparing to install screen comes up and then it just sits there, I let it sit there once for two hours, it does say that it is not responding yet it does nothing...

Sounds Good can you tell me also how I can implement this SQL in my report. I am very new at this and could not figure out how to use the information you gave me. Thank you.

I have 20 products lines, each product line has serial numbers assigned. Each serial number takes up to a year to produce and are in various stages of production. I must give a weekly report on over a 100 different products. My report needs the last data entry for each serial number grouped...

I finally got it. Thanks for all your help. On my command button in the form that says abort. I have the code DoCmd.RunCommand acCmdUndo DoCmd.RunCommand acCmdClose This does the trick no files added probably do not even need the undo but I'll try that later. Again thanks to all who...

The DoCmd.RunCommand acCmdUndo works great except that it still adds a blank record to the data base. I would prefer not to have this blank record.

I need to have this undo or not save when I click on an abort button in the form. The user should just say I don't really want to make this entry so I am clicking the abort button and the record is not saved.

Sometimes I am in a form and need more informations so that I want to make the entry at a later time but I cannot quit without creating a new entry which is incomplete and I don't want to keep. How can I quit without saving the current record entry information?

I found the answer myself. It was a syntax error in one of my double click event procedures. The name of the procedure at the top did not match the name at the bottom of the procedure. This affected all of my double click procedures while the error was only in one of the twenty or so for that...

I found the answer myself. It was a syntax error in one of my double click event procedures. The name of the procedure at the top did not match the name at the bottom of the procedure. This affected all of my double click procedures while the error was only in one of the twenty or so for that...

The expression On Dbl Click you entered as the event property setting produced the following error: Member already exists in a object module from which this object module derives. I know the dbl click procedure was working for employee names, manufactures, and assests. Where is you double...

The expression On Dbl Click you entered as the event property setting produced the following error: Member already exists in a object module from which this object module derives. I know the dbl click procedure was working for employee names, manufactures, and assests. Where is you double...