> I have a client on OfficeXP. I am trying to do a couple of updates and fixes
> and in one of the queries I am writing (my system is on '03), I am using the
[quoted text clipped - 5 lines]
>
> Advice is appreciated.
My MSWord 11.0, MSOutlook 11.0 and Office 11.0 are checked. I also have VBA
checked and VB Extensibility 5.3 checked.
Wouldn't 11.0 checked cover what was necessary in 10.0? If I uncheck 11.0
and check 10.0, my application won't run because of some of the code.
I did a compile and compact as was suggested in a thread from last April.
That did not resolve the problem.
> Make sure that the reference for "Visual Basic for applications" and
> "Microsoft Access 10.0 Object Library" are checked. When I started working
[quoted text clipped - 10 lines]
> >
> > Advice is appreciated.
Michael Suttkus, II - 15 Nov 2005 20:01 GMT
Yes, those should be sufficient.
Since I haven't worked with the 11.0 object set, you may have to depend on
someone else for answers. My best remaining guess is to remove the $ from
the function. The $ is really a holdover from the old BASIC days when it
identified string functions. In the 10.0 object set, "Left(" works just was
well as "Left$(". Perhaps they decided to stop supporting the older form in
favor of the new one.
> My MSWord 11.0, MSOutlook 11.0 and Office 11.0 are checked. I also have VBA
> checked and VB Extensibility 5.3 checked.
[quoted text clipped - 19 lines]
> > >
> > > Advice is appreciated.
Lynn Trapp - 15 Nov 2005 20:10 GMT
I believe that Access 2003 no longer supports the Left$ function. The Left
function does exactly the same thing.

Signature
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html
> My MSWord 11.0, MSOutlook 11.0 and Office 11.0 are checked. I also have
> VBA
[quoted text clipped - 26 lines]
>> >
>> > Advice is appreciated.