[AccessD] Patch problem?

...is the dao reference before the ado reference on both systems?

William

--------------------------------------------------
From: "Jim Lawrence" <accessd at shaw.ca>
Sent: Monday, May 17, 2010 2:20 PM
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Patch problem?

> Hi Rocky:
>
> I can not produce the error at this moment as it can only be produced on
> certain machines on certain client sites... and they are very busy right
> now.
>
> The computer in question, has a fully patched XP SP3, Access 2003, all
> references match one to one to a system without issues. Reference issues 
> are
> usually my first suspect when things go sideways but not so in this case.
>
> I can not remember the precise error as it was very late last night when I
> uncovered it but paraphrasing the error "'mid(' is not a valid reference"
> would be an approximation of the error.
>
> Jim
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
> Sent: Monday, May 17, 2010 11:06 AM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Patch problem?
>
> What error?  Usually when I see this it's because of a missing reference.
>
> Rocky
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
> Sent: Monday, May 17, 2010 10:53 AM
> To: 'Access Developers discussion and problem solving'
> Subject: [AccessD] Patch problem?
>
> Hi All:
>
> Has anyone else ran into the 'mid, left and right' errors?
>
> I have had this problem pop up from time to time on a variety of MS Access
> applications.
>
> Sometime it takes a while to actually get the system to respond with an
> error message but an odd display may trigger an investigation and then
> drilling down usually uncovers the source.
>
> Most times I have been able to code around it, sometimes it will only 
> affect
> one or maybe two desktops in a whole site. It usually shows up when there 
> is
> a very complex piece of code or sequel request.
>
> Sometimes the problems can be resolved by pre-processing some of the data
> before some heavy number crunching. Other times by recompiling on the
> client's site... Other times by repeatedly applying patches.
>
> I have had the same problem with Access 2000, 2003 and 2007 on Windows OS
> XP, Vista and Windows7
>
> Is this just me or have others run across the same problem? Is there a
> resolution or a specific cause?
>
> Any comments or help would be greatly appreciated.
>
> Jim
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>