Search results for query: *

Where do you wish this "comment" field. In the subform? In this case, you could build it using the RecordsetClone property in an event procedure of the subform (Load or Activate) >>DIM Comment as String >>Comment="" >>Me.RecordsetClone.MoveFirst >>DO WHILE NOT...

Simple but needs to use VBA procedures: 1) In an independant module, create 5 Public variables for your 5 criteria with their appropriate data type. 2) In your form, before to launch the Report, transfer the value of the input boxes to the public variables 3) still after to launch the report...

Not sure it solve your problem but in such situation, I use to base the subreport on a query where a condition operate on a field of the Report. That is a Where clause in the SQL string of the query containing something like: (T_Active.Day)=[Reports]![L_Plan_Week]![ZT_PlaWk_Day]) and it did run...

It is that easy to help without having a look.... When it's acceptable for you, the simplest approach from the original situation, where a detail section includes every data on the product, the ImageID, and the image itself, is: Add in Grouping/Sorting a Sort by ImageID with a GroupHeader. In...

you can achieve that with a cross tab on an Union query. I supposed your table contains the fields Year_Fig, Expenses_Fig, Income_Fig, Net_Fig Creat a Union Query with the following SQL string: SELECT "Expenses" as Line_Ident, Year_Fig, Expenses_Fig as Line_Figure FROM Q_Test UNION...

Where is the filter parameters? In the Data tab of the parameters of your report You have a parameter called Filter where you write your condition: Status="R" and a second one called FilterOn to set to YES Try once that way to be sure you're in the right way. Then you can write a more...

You don't have to create a group header, just sort by Image_ID THEN PartNumber. Do not declare any Group Header/Footer. THe section will disappear for your design. Normally you should get a continuous report, in the right order. And, you're right to be cautious, then you can try to make the...

YES Access begin with the first record (row). The quickest way is to supply data to your report through a Query with the Operation parameters set to Last for each of you 3 fields. So the query does only contains the last row and the report has no choice but to print it!

Declare your Manager variable as a Public variable in a VB Module (not a form module, an independant module). If you have not, create a new one only with the declaration of the variable. >>Public Manager As Boolean Then, do not declare it on any modules attached to your both forms. Is should run!

Start solving some issues by creating a Group (with the Grouping/Sorting dialog) based on the Week field (or a formula like =Week(Date_Field) if the field in your record contains the full date). In the GroupFooter section created you can easily add some text boxes with =SUM (SomeField) to print...

OK, clearer! BUT... I have no other suggestion that the ones I gave you last night or something like that move this form launched from the report to a form closed before the report opens. For sure I can't appreciate how tricky it is to make such a move!

What you can use to reach your goal is to add in lieu of a second Report Footer is a GroupHeader based on a constant field. Such a section will print only once, at the end of the report. If there is no such field in your RecordSource, add it to the request by creating a new column: Always_Same...

I'm a little bit surprised you open a modal form in the Report_Open - why there? - and wait till the Report_Close to close it? A suggestion: Why don't you select the parameters (Group/sort and criteria) in your main form, put them in Public variables and further get them from these variables in...

Probably you have built a Report with a Detail section containing a field with the image and some other with your products information, and set a Group based on ImageID with PageBreak set to YES. A way to achieve the hidding of duplicate image: 1) Declare a variable of the same type as the...

????Why not use the PageBreak parameter of the ReportFooter? Because you want it in the same page when it fit? In this case have you try the KeepTogether parameter in the Report Footer section? What's wrong?

Are both fields referenced in the expression (Negotiable & Minimum Salary) fields in the reports? To find the problem, separate it: make a trial with only one part of the condition =IIf (Negiotable<>0; &quot;NEGOTIABLE&quot;; [Minimum Salary]) then with the second =IIf ([Minimum Salary]<>0...

The quietest way is to attach the remote ODBC table and to build the RecordSource parameter on the attached table. When you can't, build a query to try the SELECT statement before you use it in your Report - you'll see the records returned. You have to create an SQL-Direct query. Once running...

That's what the Where Clause aims. You'll find them both in Macro and in the VB code DoCmd.OpenReport &quot;Report_Name&quot;,,,Where_Clause The content of the string WhereClause depends on the way you select the record(s) to br printed. Its syntax is described in the Where clause of the SQL...

A lot! So, could you be more specific? What you mean be can't edit? which error message/code? What do you mean by edit? -Change the form features in Design mode? -Change the contents of some fields? Do you protect your database? Has both users (the one that can, the other that can't) the same...

Are you sure that the callbarcode function is typed &quot;String&quot;? What don't you use the Uppercase function: =UpperCase(Callbarcode(UPC_Code)) Appears too simple-Does I miss a step?