MartyConnelly
martyconnelly at shaw.ca
Sun Mar 13 01:19:33 CST 2005
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 For gory details on P-Code and canonical text (source code) in compilations http://www.trigeminal.com/usenet/usenet004.asp?1033 You might have to use the command line /decompile method to get things sorted out This will remove all the compiled p-code from the mdb go to Run and type in cmd then type in appropriate version of this line below or cut and paste to paste in the cmd window use a right click "C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "D:\FullPathTothe\Database.mdb" /decompile Or Check her menu -- > help--> about Microsoft Access to see if form says Microsoft (R) Access 97 SR-2 Kathryn Bassett wrote: >No recompile because I didn't use any macros etc so didn't think about it. Too late to do it in 2k as she's now making changed in 97 version. So, what menu and command needs to be one on the 97 version to "compile" it? > >-- >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 4:58 pm >>To: Access Developers discussion and problem solving >>Subject: Re: [AccessD] 2000 vs 97 - trim error >> >>I opened up the 97 version mdb, reports are okay on my >>machine I am running WinXP Home Access 97 SR-2 and Jet SP 8 >>It could be Service Packs or did you remember to do a full >>recompile of 2000 before converting to 97 >> >> >>Kathryn Bassett wrote: >> >> >> >>>Friend has Access97, and the data she's been using for a >>> >>> >>couple years now has been working fine. She received a new >>grouping of people, so I brought her 97 home, opened with 2k, >>imported and set up the new table (members), made a query and >>set up one of the reports. Everything working fine in 2k. Did >>the save to previous version, went to her house and put back >>on computer. Queries and forms work fine, but when I tried to >>do reports, the all give me this trim error. >> >> >>>http://www.ourwebsite.org/storage/misc/trimerror1.jpg and >>> >>> >>here is what >> >> >>>the design view looks like >>>http://www.ourwebsite.org/storage/misc/trimerror2.jpg >>> >>>All the reports are similar, and give the same error, even >>> >>> >>though I never touched them. So it must be something about >>taking from 97 to 2k and back again that messed things up. >>What's wrong and how do I fix? >> >> >>>If you need to see the actual mdb, I've zipped both versions >>> >>> >>and put them here: >> >> >>>http://www.ourwebsite.org/storage/misc/pgch.zip >>> >>>Thanks, >>> >>>-- >>>Kathryn Rhinehart Bassett (Pasadena CA) "Genealogy is my >>> >>> >>bag" "GH is my >> >> >>>soap" >>>kathryn at bassett.net >>>http://bassett.net >>> >>> >>> >>> >>> >>-- >>Marty Connelly >>Victoria, B.C. >>Canada >> >> >> >>-- >>AccessD mailing list >>AccessD at databaseadvisors.com >>http://databaseadvisors.com/mailman/listinfo/accessd >>Website: http://www.databaseadvisors.com >> >> > > > -- Marty Connelly Victoria, B.C. Canada