Replies

Excellent. Thanks Hans. It works great!

Thanks. That works great.

Doug, one other issue has come up. In many cases if the CloseDate is prior to the actual DueDate or ExtDate it results in a (-) number. When I total all of the number up to calculate how many of the corrective actions were overdue, and by how many days total, and how many days average, the (-) number sqews the final numbers. How can I translate the (-) number into a “0” so it doesn’t affect the calculated numbers.

Great. Thanks Doug.

Great. Thanks for the help.

I’m using a Send Object command in a macro. It opens up a replica of the Invoice form in a Report format, saves it as a .snp file, places it in the email, etc. Does that help out? Like I mentioned, it works great. Just trying to figure out how to save them from having to enter email addresses in both the Customer Info form as well having duplicate copies in their Outlook Contacts. Multiple users use the database so keeping all the data self-contained would be a big help.

Well when all else fails, generate a new database. Which is what I did to correct the problem. Imported all objects and data and it works great. Ahhhh those problems which creep into Access and can never be fixed………

No. Since it worked before on the same PC’s I’m not sure how changing the viewable records from 1000 to 10000 would affect the references. But to be on the safe side I will ask them to check. I guess the question is how would I know which one may not be installed? In the past when I’ve run into reference problems the error message indicated which “reference” was not loaded.

Thanks guys. Works great.

Works great. I did have to insert the

DoCmd.Echo True, “”

line in before the Exit Sub or the screen would be frozen. Thanks for the help.

Great. Thanks, it works fine. Second question then. Is it possible to use code to disable the Macro functions under the “Tools” menu, so that the user cannot open the Visual Basic Editor to see the password in the code. Naturally it would be for only this heavily used sheet only.

I guess you did understand cause what you provided works great. Thanks Charlotte.

Once you use Jet Comp and/or generate a new database and import all the current information, I would suggest using the “table-splitter” add-on and get the database into more manageable “chunks”.

Make sure you delete all of the filtering events found in the Form properties under the OnOpen, and OnUpdate properties. These events still cause the form to “look” for the options table.

Access Runtime for the most part will allow normal functionality of Access DB’s. However there are cases directly related to use of the Switchboard Manager to develop the application switchboard, where the application will not operate properly in Runtime. I have been down this path several times myself.

There are two solutions: you will either need to add the switchboard manager “add-in” onto the PC’s with runtime, or the easier solution to save future hassles, is to convert the switchboard buttons and labels over to VB or macro driven. Change them over from the current =option value that relies on the underlying Switchboard table to make them work.

This should fix your runtime problem.