Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

weird error message

Status
Not open for further replies.

leeroi

Technical User
Jun 5, 2000
122
US
I have installed an Access 97 database on 25 workstations at my office. The database runs fine on 24 of them. All machines have Office 97 Professional. On one machine, the database runs fine with the exception of one form. When I try to run it, I get the following error message: &quot;Function or interface restricted, or th function uses an Automation type not supported in visual basic. <br><br>I have run repair/compact, reinstalled the database, and uninstalled/reinstalled Access but I still keep getting this error. Obviously, it's a problem with something on this particular machine since the database runs fine on the others. I'm at a loss as to what else to do. Any help would be appreciated.<br><br>Lee
 
Hi Lee:<br><br>Does the form open on that machine?&nbsp;&nbsp;When does this error occur?&nbsp;&nbsp;Does it use any activeX controls which aren't registered on the machine?&nbsp;&nbsp;<br><br>You might want to try Ghosting a machine that works onto that machine. That is, making an exact duplicate of the hard drive of one of the machine that works and putting it on the one that doesn't.&nbsp;&nbsp;<br><br>I had one machine that had the identical problem when I used a commondlg control on a form.&nbsp;&nbsp;My solution, because I didn't have access to a the machine (I was in another state) was to rewrite the form to ensure the problem wouldn't recurr.&nbsp;&nbsp;I used API calls for the open menu rather than the common dialog control.&nbsp;&nbsp;Now the form works on any pc.<br><br>I hope that helps!<br><br>Karen
 
The form consists of a main form with an unbound control that I use to filter records in the subform. Here's the code that the error message points to:<br><br>Sub Combo21_AfterUpdate()<br>&nbsp;&nbsp;'Find the record that matches the control<br>&nbsp;&nbsp;Me.RecordsetClone.FindFirst &quot;[StaffID] = &quot; & Me![Combo21]<br>&nbsp;&nbsp;Me.Bookmark=Me.RecordsetClone.Bookmark<br>End Sub<br><br>The&nbsp;&nbsp;& sign is highlighted when I run debug. Unfortunately, when I get to this level, my coding skills are pretty much Null.
 
Ok Lee:<br><br>This looks to me like code generated with a wizard.&nbsp;&nbsp;You could try two things.&nbsp;&nbsp;1) If the data type of StaffID is text then Change the code to this:<br><br>Sub Combo21_AfterUpdate()<br>&nbsp;&nbsp;'Find the record that matches the control<br>&nbsp;&nbsp;Me.RecordsetClone.FindFirst &quot;[StaffID] = '&quot; & Me![Combo21]& &quot;'&quot;<br>&nbsp;&nbsp;Me.Bookmark=Me.RecordsetClone.Bookmark<br>End Sub<br><br>2)&nbsp;&nbsp;If that doesn't help, try to add the code again using a wizard.&nbsp;&nbsp;<br>&nbsp;<br>If nothing else you will see how the wizard changes the code for you.&nbsp;&nbsp;&nbsp;<br><br>Hope that helps.&nbsp;&nbsp;I would need more specifics to answer better.<br><br>Karen
 
The plot continues to thicken. The Staff ID is a number.<br><br>I went into the form and deleted the unbound control, then recreated it. When I clicked on the After update property and began writing in the code. As soon as I tried to enter the first line (me.recordsetclone.....) I received an error message indicating an IPF in VBA32.dll. Each time I tried to enter code I got the same error message. I replaced the VBA32.dll file with one from another computer, but still get the same message.<br><br>I can't find anything in the MS Knowledge base about this problem.<br><br>What now?
 
The only thing I can think to do is ghost the image from another pc that has no problems.&nbsp;&nbsp;That is, save any data from the PC such as local documents, etc, then copy the OS with a ghost software onto the PC.&nbsp;&nbsp;I've had similar problems and this is the only sure way we had found to fix it. <br><br>Some of our PC's had Office 97 installed over 95 and we had problems with that.&nbsp;&nbsp;We then had to wipe the registry of any connections to 95.&nbsp;&nbsp;It is easier to just create an image from a fully functional PC and reimage that machine.<br><br>Hope that helps.<br><br>Karen
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top