Search results

Usually this means that somehow your page layout got to be wider than the print page. Check your report definition carefully & then look at the size of your print page (margins & such...)

Well, I just set up different reports, each one covering a different size of label...

Same way you handle this in any report. You need to have some field that you can use to identify where the break should be, and sort on that field. Then go to "sorting and grouping" under "view", and add that field to the list. Give it a group footer. Then in your report, for the...

OK, can I assume that you are using a top values query to get the first 10? And also that there is some flag or other value that you are checking to see if a unit needs testing? Then, assuming that the users update that value, your next run of the top values query would give you the next ten...

What is your "Receipt" report based on? You need to create a query that will select data (one record) based on whatever receipt ID is on your form. Then change the source for your "Receipt" report to that query. If your field names are the same, this is an easy change.

If you copied your "iif" into your question correctly, you have a syntax problem. You are supplying a value (in this case, "") for the function if the field is null, but nothing if it is not null. Try something like this: Iif(isnull[Fieldname]),"",[FieldName])

Create a query that will use the client ID from your form as its criteria, bringing back just that 1 record. Then base a report (which will create the label) on that query. Put a button on your form to print that report.

Have you tried bringing up the properties for the entire report & just changing the Record Source? If your field names are the same, you should have no problem.

KevinM is right...the idea is that you never store a field in a table that is really a calculation. This is a basic tenet of database design. In this case, you have a field somewhere that says how many places there were to start with, right? Then you create a query that will sum up the places...

Just a guess: Dim myFilter as Variant Dim myPeriod as Variant myPeriod = Me.Period MyFilter = "[Period] = '" & myPeriod & "'" DoCmd.OpenReport ("R_Standard Monitoring Report"), acViewPreview, , myFilter

Well, from what I hear, if you really want to use Access buttons, there aren't many options. On the other hand, you can put VBA code into the "on click" (or "mouse move" or ...) event of labels, images and lots of other form items. You can even put "invisible" boxes on the screen and make...

Start with the query. Look up parameter queries in the Access help, that's what you want to build. When you get the query to bring back just the records that you want, build a form based on that query. You'll need to make a little change to the query itself, so that instead of asking the...

You could create a new field in the query underlying a report, like this: NewField=Iif([TABLEA]![MyField] ="X", [TABLEA]![MyOtherField] ," ") You could put similar Iif code into the Control Source of a report field, if you'd rather do that.

I think that what you want to do is to keep your value as a variable, not a constant. A constant can never change: "By declaring a constant, you can assign a meaningful name to a value. You use the Const statement to declare a constant and set its value. After a constant is declared, it cannot...

One question: Why? Typically, this is done by using a parameter query as the report source, or by using a filter. Is there a good reason that these methods won't work? Both methods dynamically create the report input.

Actually, there is another way to store the prices. Make each oil price its own record in a table, with beginning and ending dates ("effectivity dates") for that price. Then you can calculate the price at any given point in time. You can also put price changes in ahead of time (give them an...

My guess is another set of parentheses (spelling???). Try this: GetValue: IIf(([EarnCode]=1 or [EarnCode]=2), IIf([extrate]>[pwrate], [extrate],[pwrate]),0)

Easiest way...Set up a global variable ("Dim Public strMyField as string"), set that field to your value in the first form, use that field in the second form. Also, you'll save everyone else's hairline if you run spellcheck before you post.

Try something like this: stSubject = "\\Serv001Mkt\Orders\Comp\stOrderNum" Then use that in the OutputTo. Right now, Access thinks that your stSubject in the OutputTo is just part of the literal...

I'd use Dlookup to see if the name is in the other table.