[AccessD] [Fwd: Re: [Fwd: Re: Incompatibility?]]

-------- Original Message --------
Subject: 	Re: [AccessD] [Fwd: Re: Incompatibility?]
Date: 	Wed, 05 Apr 2006 19:22:26 -0700
From: 	Rocky Smolin - Beach Access Software <bchacc at san.rr.com>
To: 	Access Developers discussion and problem solving 
<accessd at databaseadvisors.com>
References: 	<4431457F.1090400 at san.rr.com> <44318727.4040100 at shaw.ca>



Marty:

Thanks for all that.  The guy I'm working with is in Bangalore.  His 
problem site is, I think, in Hyderabad.  And in Hyderabad, they don't 
have broadband.  So I can't send him anything there but short emails.  
So it will take a while for this to unfold.  I'll be a dollar it's a DLL 
problem.  Maybe a reference issue which your code will uncover.  It's at 
least Access 2000.  That's not a 'lower level of Access' is it?

I'll let you know if something interesting turns up.

Best,

Rocky


MartyConnelly wrote:
> You might get this with ArcInfo as it uses Access as one of its data 
> engines,
> so you might get a bum DAO reference on an install, don't know about AutoCAD
> AutoCAD might also might forece an install of an old common control.
>
> This might help
>
> Stick this code in an mde and run on the odd machine.
> It will printout the possible reference differences (version number, 
> path and name).
> Or rewrite this inorder to dump to a text file like
> 'kill file as necessary
> Open c:\temp\outputref.txt For Output As #1
>      Print #1, ReferencePropertiesList
>      Close #1
> Run it from autoexec macro, code should be fully disambiguated to avoid 
> any initial reference check
> before running. ie VBA.MsgBox, Access.Reference and VBA.Len, VarPtr 
> might not be available in lower versions of Access
> might be a replacement on www.mvps.org/access
>
>
>