Bobby Heid
bheid at appdevgrp.com
Tue Apr 13 08:50:33 CDT 2004
Hi Gustav, Thanks for reminding me of this issue. I was off work Friday and Monday and had forgotten to let everyone know that I solved the issue on Thursday, right as I was leaving for the weekend. <RedFace ON> This particular report has six 'tiers' (0-5) on it. And after reviewing the report, I found that it does not use the Notes (memo) field. So I modified the queries to remove the Notes field. When I then went to run the report, it gave me the missing field error (it was saying the Notes field was missing). I tracked the error to a field that should contain estimated receipts. I guess when I had been setting up that last tier, I had accidentally clicked the Notes field as the data source instead of the correct field. DOH! And since it is rare for the client to have a tier 5 record (and one with a note), no one had caught this error before. So basically, I screwed up the report. <Head hung low.> </RedFace ON> Thanks to those that looked at this issue with me. Bobby -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock Sent: Tuesday, April 13, 2004 7:28 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Wierd AccXP memo happenings. Hi Bobby 1. What happens if you attach the memo content to another record? 2. Try to locate what part of the memo causes the blow. You do that by cutting it in two, then try with the first and then with the second part; continue along this road with the part that fails until you have tracked the malfunctioning part. This may tell you something. /gustav > Hi all, > I have a query that pulls data from several tables. Been running well > for years. I get a call on Monday that it will not print all the way. > So after some researching, I found out that the report was blowing up > when it got to a certain page. > What was happening is that the data from this one table is all of type > double. BUT, for some reason, this one record is returning with the > data from a memo field from the same record (not pulled in the query) > and is blowing up where I am trying to keep up with some totals. > I can delete the data out of the memo and the query runs correctly. I > past back the data and it blows up again. So, I save the memo data in > notepad, remove it from the record, compact the database, import it > into a new database, then add the data back form notepad, and it blows > again! > Any ideas (short of moving the memo field to its own record) on how to > fix this sort of problem? It runs great on 100+ other database (all > back-ends). > Thanks, > Bobby -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com