Susan Harkins
ssharkins at bellsouth.net
Fri Jun 25 09:47:48 CDT 2004
Late-binding -- that's really it. I tried the Access prefix -- didn't make any difference. Seems it's in 2000 and 2002 -- if it's a project library, the code catches it, if it' typelib library it throws an error. 2003 is fixed. Oddly enough, 97 seems to work OK -- now that truly confuses me. :) Susan H. Hi Susan What's the cure for this bug, if any? /gustav > Turns out it's a well known bug -- but I'll check this out too -- > can't hurt. > Susan H. > Hi Susan > I have not an Access 2000 installation right on hand. > Similar code works here with the minor difference that Access is > preceding > "everywhere": > Dim ref As Access.Reference > .. > Access.Application.References > /gustav >> An editor's having trouble with the Remove method in 2K and XP. I was >> able to re-create it by running an Access 2003 db with a reference to >> Excel 2003 on a system with Access 2000 and no Excel. The error says >> the object doesn't suppor the method -- and points to the Remove >> method, but it's there in Intellisense. >> It's only 2000 and 2k -- any ideas? >> Susan H. >> Sub RemoveBrokenReferences() >> 'Find and remove broken references >> Dim ref As Reference >> For Each ref In Application.References >> If ref.IsBroken = True Then >> Application.References.Remove ref >> End If >> Next >> End Sub -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com