From: Repent34 on 5 May 2010 15:27 Gina; on my laptop, I have MS Access 2007 installed. I have also installed the "developers extensions" as well as the "Save as PDF or XPF" add-ins. The client workstations only have the Access Runtime installed. The references I have installed on my W/S, by looking in the MS Visual Basic Editor/Tools/References are: Visual Basic for Applications Microsoft Access 12.0 Object Library OLE Automation Microsoft Office 12.0 Access database engine Object Library Microsoft Outlook 12.0 Object Library chris On Tue, 4 May 2010 19:56:51 -0400, "Gina Whipp" <NotInterested(a)InViruses.com> wrote: >Oh dear... missed that last line, no you can't but it surely sounds like a >Reference issue. Okay, when you open the database on your machine what >References are set? > >As a side note, stop using your real eMail address as the Spammers will >harvest!
From: Repent34 on 5 May 2010 16:11 I've done quite alot of testing on this issue. what I've found out, is that if I remove a sendmail macro action from a button on a form, as well as removing the VBS code under the editor, save everything, create another accde file and publish to my client, I now don't receive this error, and everything seems to be back to normal, except of course when the user clicks on the button, to drive the macro that does a send mail funtion, nothing happens. I just need to fix that part. I'll try to do this and post back my results. the T/S I did consisted of removing various parts of my forms, code, controls, etc until I removed the above referenced control for sendmail that resolved the issue. Do this sound familiar to anyone? chris On Mon, 3 May 2010 19:36:10 -0400, "Gina Whipp" <NotInterested(a)InViruses.com> wrote: >Check the References on your Client's machine. Sounds like ther might be >one missing.
From: Repent34 on 5 May 2010 17:23 Looks like my issue is finally resolved. I ended up having to remove the macro for the sendobject, in this case, email. I then recreated it from scratch and everything is back working. If there is an easier way to discover the problem, I sure wish someone would share it with me. I may run into this issue again. BTW, I had tried creating a new blank DB, then importing over all forms, controls, queries, etc. Still had the same error. Only after deleting the macro and underlying code and recreating it did I get a solution. chris On Wed, 05 May 2010 13:11:59 -0700, Repent34 wrote: >I've done quite alot of testing on this issue. what I've found out, >is that if I remove a sendmail macro action from a button on a form, >as well as removing the VBS code under the editor, save everything, >create another accde file and publish to my client, I now don't >receive this error, and everything seems to be back to normal, except >of course when the user clicks on the button, to drive the macro that >does a send mail funtion, nothing happens. I just need to fix that >part. I'll try to do this and post back my results. > >the T/S I did consisted of removing various parts of my forms, code, >controls, etc until I removed the above referenced control for >sendmail that resolved the issue. > >Do this sound familiar to anyone? > >chris > > > >On Mon, 3 May 2010 19:36:10 -0400, "Gina Whipp" ><NotInterested(a)InViruses.com> wrote: > >>Check the References on your Client's machine. Sounds like ther might be >>one missing.
From: Gina Whipp on 5 May 2010 22:39 Not sure what happened with SendObject... and that is not a Reference issue. Unfortunately, tracking down errors is sometimes tedious (and annoying). Did you change anything in the macro that would indicate what part thru up the error? -- Gina Whipp 2010 Microsoft MVP (Access) "I feel I have been denied critical, need to know, information!" - Tremors II http://www.regina-whipp.com/index_files/TipList.htm "Repent34" wrote in message news:08o3u5hjcf8kgipl83evtf8mp44u8iujij(a)4ax.com... Looks like my issue is finally resolved. I ended up having to remove the macro for the sendobject, in this case, email. I then recreated it from scratch and everything is back working. If there is an easier way to discover the problem, I sure wish someone would share it with me. I may run into this issue again. BTW, I had tried creating a new blank DB, then importing over all forms, controls, queries, etc. Still had the same error. Only after deleting the macro and underlying code and recreating it did I get a solution. chris On Wed, 05 May 2010 13:11:59 -0700, Repent34 wrote: >I've done quite alot of testing on this issue. what I've found out, >is that if I remove a sendmail macro action from a button on a form, >as well as removing the VBS code under the editor, save everything, >create another accde file and publish to my client, I now don't >receive this error, and everything seems to be back to normal, except >of course when the user clicks on the button, to drive the macro that >does a send mail funtion, nothing happens. I just need to fix that >part. I'll try to do this and post back my results. > >the T/S I did consisted of removing various parts of my forms, code, >controls, etc until I removed the above referenced control for >sendmail that resolved the issue. > >Do this sound familiar to anyone? > >chris > > > >On Mon, 3 May 2010 19:36:10 -0400, "Gina Whipp" ><NotInterested(a)InViruses.com> wrote: > >>Check the References on your Client's machine. Sounds like ther might be >>one missing.
First
|
Prev
|
Pages: 1 2 Prev: Anyone who can help my fried mind with this solution? Next: 2 independent criteria |