Stuart McLachlan
stuart at lexacorp.com.pg
Fri Oct 11 19:45:04 CDT 2013
So does running the program from a batch file which copies a master FE to My Documents or whatever and using that clean copy each time. Or using a separate scratch database with linked temp tables. There are several options depending on your particular cirumstances. ( I tend to use the first option above in multi user environments. It has other advantages as well). -- Stuart On 11 Oct 2013 at 17:16, Rocky Smolin wrote: > Compact on exit works. But there is that annoying lag between exiting and > the app actually closing. > > r > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan > Sent: Friday, October 11, 2013 5:13 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Access Report - One field for one Customer is Missing > > But be aware of bloat and come up with some way to handle it. > > On 11 Oct 2013 at 16:55, Rocky Smolin wrote: > > > I've used that work-around myself when faced with a report that's > > going to require overly complex queries. Not your case exactly but I > > got the idea of the temp table years ago from this list. I like the > > temp table approach because you can lay out the table with exactly the > > fields you want on the report and populate t with data instead of FKs. > > Use a bit of code to open a recordset to get the basic data - loop > > through it filling the target table and walla! Report. > > > > Rocky > > > > > > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brad Marks > > Sent: Friday, October 11, 2013 12:50 PM > > To: Access Developers discussion and problem solving > > Subject: Re: [AccessD] Access Report - One field for one Customer is > > Missing > > > > Rocky, David, Gary, Doug, > > > > Thanks for all of your ideas/insights. > > > > I used every idea as I tried to debug this problem. > > > > One thing that I failed to mention earlier is that the underlying > > query is pulling data from several other queries. In other words it > > is complex. It appears that when the complexity of the queries is > > combined with the report (which has sorts and filters), the Access gods > are angered. > > > > I changed the report's query to be a "Make Table" query and then I > > changed the report's data source to this new temporary table. This > > fixed the problem. > > > > I don't fully understand what Access does behind the scenes, but > > apparently the underlying queries are somehow combined with the report > > filters and in some cases that does not work properly. > > > > I really appreciate all of the help. I am the "Lone Ranger IT person" > > with no one else onsite to consult with. Your assistance on this > > issue and on many prior problems has been outstanding. > > > > Thanks again, > > Brad > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > ~~ > > ~~~ > > > > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brad Marks > > Sent: Friday, October 11, 2013 11:23 AM > > To: Access Developers discussion and problem solving > > Subject: [AccessD] Access Report - One field for one Customer is > > Missing > > > > All, > > > > This is one of the strangest things that I have seen for a long time. > > > > We have a Sales Order report that has been used for several months. > > Recently one of our users pointed out that the Customer Name was not > > being shown for a specific customer. > > > > There are 7 fields shown for each customer on the report. All of the > > fields are shown for all customers, except one. For this one > > customer, only 6 of the 7 fields are shown. > > > > Here is where things get really interesting... > > > > When I look at the data from the underlying query, I can see all 7 > > fields for this customer. > > > > In other words, all of the data is visible in the Report's data source > > (underlying query), but not all of the data is being shown on the report. > > > > Any ideas or suggestions would be appreciated. > > > > Thanks, > > Brad > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > > > -- > > This message was scanned by ESVA and is believed to be clean. > > Click here to report this message as spam. > > http://h0stname/cgi-bin/learn-msg.cgi?id=F150F27DED.CF9D0 > > > > > > > > -- > > 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 > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >