Search results

Have you considered combing the fields in the query and then referring to the combined field in the report? Is this an option? Andrew

I haven't read the other posts in this thread in any detail, so in the event it is still relevant then 'yes' it would go in the report footer. Sorry for not clarifying that.... A

Hi Mike I'm going to have to make some assumption here, so assuing your report is based on a query (say 'qry_Stats') and your field on your report (and in your query) is called something like 'RunOrPass' then the percentage of run plays over all plays would be something like this ...

Can you post your SQL for this query? You can get to it when in the query design screen by clicking on View -> SQL View. Andrew :)

Why don't you like using macros? Modify your code to include the other query by inserting a new line and entering something like this after the archive query line : DoCmd.OpenQuery "qry_delete_archive_cust_data" In fact I would probably re-write the main part of the code such that it looked...

Hi Does the tax value condition over-ride the country conditions? If condition 1 is met and B & C are enabled, does the tax value condition over-ride the country settings for B or C? Also, if condition 2 is met, then B & C are already disabled so why is the tax value test required if...

What formula have you used, and where did you place it in the report? Andrew

Rather than just using something like [Enter Cutoff Date] as the criteria in q1, create a new field in your query called "CO_Date : [Enter Cutoff Date]" (without the quotes). Make sure you have the identical wording in this new column and under the field that you are using this criteria (just...

Hi Steven Have a read of this post - it discusses a very similar situation and allows you to keep your 3 keyword fields. Andrew :)

Hi This table structure almost makes perfect sense and is appropriate for the multiple hierarchy situation that you described. I'm not sure of the necessity of the 'List ID' field where every value is 1, it seems to be redundant unless you have multiple lists (which is the point of the...

How about posting the SQL for your dud query? Andrew :)

Try using a format (in your field on the report) of 0.00; -0.00 If that doesn't work, try setting the format in the query. HTH, Andrew :)

Hi If you use your scheduler to open the database, then you can do it like this : Create a new macro, save it as "Autoexec". Click View -> Macro Names and Click View -> Conditions. Starting from Top left and working across and then down, enter the following : Macro Name Condition Action...

Hi Max When you create the delete query (Click Query -> Delete Query), click and drag the * from the table into query grid, it should show 'Delete' in the 'Delete' row. This will delete all records. To only delete the records where archived =yes, add the 'archived' field into the query grid...

Hi Max In a nutshell : you are on the right track. These are just my thoughts on the scenario you described - other posters may have other opinions, but this is how I would approach it. In your data table(s) have a yes/no field called archived (default = no). When the user wants to archive...

Hello You can extract the part of the postcode before the space with a new field in your query like this : Left([PostCode],InStr([PostCode]," ")-1) Make sure you use your actual field name where I have assumed 'PostCode'. You can then group by this field in a totals query and count the...

Hi I had a similar issue (An apostrophe makes the DLookUp function crash and burn) and I stripped the apostrophes out. This looks like a much better way of handling apostrophes, but I have a question. If you are referring to a control on a form, rather than hard-coding the 'Smith' part, would...

Hi If you have to input inspection information for both methods / factories for each year (even though XYZ is done every 3rd year), then it sounds like there is an issue with your table design. Can you post back with a description of the fields in the relevant tables? Andrew

It sounds like you have both the 'Profit and Loss' and 'Balance Sheet' reports on one page. At some point this is going to cause problems and you will probably need to separate the two reports. To do this you need to identify the 'Profit and Loss' accounts versus 'Balance Sheet' accounts...

Following on from Pat's suggestions, here is a webpage on database normalisation, and a couple of pages on calculations in queries here and here. HTH, Andrew