Search results

Two suggestions: Have the report recipients install the free snapshot viewer from Microsoft. Use the LeBans ReporttoPDF module and output the report to pdf before sending.

Change shortcut menus to false. Also, uncheck "Allow Customizing" in the tool bar properties I just saw you are missing one property also: Change_Property "AllowByPassKey", DB_BOOLEAN, False Change_Property "AllowToolBarChanges", DB_BOOLEAN, False Change_Property...

Agreed... no need for external software.

Ok... I'll go through it and see where I'm hanging up. If I get stuck I'll give you a shout. Thank you!

Yes. We use an exchange server here at work. That makes sense now. I presume I'll have to modify my code a bit to accommodate both.

Disable your call line. Open the form you imported from my sample... Make a change. Does it work? Can you compile then?

Well, then the next step I would try is this: Disable your line again. Delete the module Import everything from the database sample that works (tables, forms, module, etc) Compile and see what happens. Try to run the audit trail in the form you just imported (just like in the example I sent)...

HitechCoach, Do you run into any compatibility issues with Access 2000, 2003, and 2007? I ask because on my work PC I have Access 2000. I can actually send email using CDO without specifying an SMTP server, etc like in your link. Bascally, I need no configuration, so the code below is...

Does the sample I attached work for you in Access 2007? Take a screen shot of the start of the module in VBA. Did you rename the Audit Trail by chance? Use the "Find" function in VBA and find out where each "AuditTrail" word is. (To find out if you have duplicate procedures). Other than that...

Did you try the 3 other ways to call the function? Put an apostrophe ' in front of the Call AuditTrail and change it to a comment. Now try to compile and see what happens. Does the sample I gave you work? Just open the sample and type some changes. Do you get the same error? It still sounds...

If you have imported the module as I have described make sure all of your references are selected: You can also try these: AuditTrail (Me.Form, [Company]) AuditTrail Me.Form, [Company] Call AuditTrail Me.Form, [Company] I agree with HiTech though, it sounds like the module is missing or...

1. Import the "mod_AuditTrail" into your database. 2. In the before update event of the form you want to track put this: On Error GoTo Error_Handler Call AuditTrail(Me.Form, [txt_Company]) Error_Handler_Exit: Exit Sub Error_Handler: MsgBox ("Error No: " & Err.Number & vbCrLf...

Here's an example of how you can do that. Good luck.

Here's something that has been giving me fits. In my work book, if I use the following in a cell, I get a count of all cells in the range that are populated: Count(C22,F22,I22,L22,O22) I am trying to do this in vba: Public Function No_Conditions(M_Range As Range) No_Conditions =...

Well, I am not sure. What I have run into is where I was using this in an Office 2000 environment: Set objEmail = CreateObject("CDO.Message") Set objConfig = CreateObject("CDO.Configuration") If sPriority = "High" Then objEmail.Fields.Item(cdoImportance) = cdoHigh...

I'm using the old cdo reference to send emails from a database. Can anyone point me to a reference or tell me how to programatically find out what the particular SMTP server is on a particular machine? Nearly all of the examples I have found hard code the server name and I want this application...

In vba, Insert a module then paste it there. In the BEFORE_UPDATE event on the FORM paste this: Call AuditTrail(Me.Form, [RecordID]) The "recordID" is your form's auto number or primary key. Having a split database should not make a difference. Just create the table in the backend then...

I don't have Office 2007, so I am unable to create in .accdb format. Using ULS is indeed an option, I do use that as well with pretty good success, as long as I am the admin. I am just honing my development skills on this. Not to mention, in this case, the project will be turned over to...

Ok... Consensus thus far is that it's not a good idea to disable the close button. I'm scrapping the idea in favor of Boyd's solution. So that is added to my to do list. Also if I am to keep the "back door" I need to make it a little tougher. Anyone have any other input? Thanks Craig

I see. I'll give that a whirl too. It also sounds like a better idea than disabling the close button. Thank you.