Kathryn Bassett
kathryn at bassett.net
Wed Mar 16 23:18:16 CST 2005
Solution is that I talked her into upgrading. Since my husband works for school district, we can get the Office2003 Pro for $200 which she can afford. So now, (well, next week after installation) I won't have to worry about things breaking since I won't have to save to previous version. Hmm, I though I had 2003 myself, I guess I'll have to hunt for it and get it installed. BTW, I tried following your various instructions and it still gave me the trim error, so the solution we ae using is not a solution for if we kept on the way we are. -- Kathryn Rhinehart Bassett (Pasadena CA) "Genealogy is my bag" "GH is my soap" kathryn at bassett.net http://bassett.net > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of > MartyConnelly > Sent: 12 Mar 2005 11:20 pm > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] 2000 vs 97 - trim error > > Just open up the code behind a report, there maybe no code > there but there is still p-code attached to the form like the > trim statement and save and compile all. But the error may > have been the uncompiled code in the 2000 version causing it > during a convert. > To test just hit CTRL -G from database window and in debug > window type ?Access.Application.IsCompiled