I created a SAP Adobe form but some fields like Price remains the same value for all of the subjects whilst it should print the respective value for each item.
I tried Modify statement but it gave nothing. Any suggestions?
Some debugging results would be nice (namely, it would be nice to know if your interface and printing program are passing correct information), but without further info I can think of 2 problems that would produce this behavior.
Error in data binding: Open design view, select table (left click top left corner), go to object palette, binding tab data binding field has to be set to your table (tablename). Select open Object palette, select binding tab and data binding field should have $.(fieldname) and NOT $.(tablename).(data)[*].(fieldname) (actual names might be different).
The above means your table element is bound to a table from context and $.(fieldname) on a row means that it is bound to a (fieldname) of a row of the table.
Second possible cause is your printing program or interface providing those details. Debug your interface, place some breakpoints and see if the internal table that contains row data has correct prices. I'm sure you know how to fix an error in code, if you find out it is an interface / program issue.
Related
This may be as simple as it can't be done, but I have to ask. :) I am building a report using Report Builder 3.0. The report contains a table which also has Grouping established. I wanted to give the user an easy way to expand/collapse all rows of the table, so I used the method of creating a parameter with two values (0 for collapse, 1 for expand), tied the visibility of the group to the parameter using an expression in the Hidden Property for the group. Then I created two text boxes for Expand and Collapse and added the respective parameter/value in the Action in the text box properties.
At this point, everything works as intended. Here is where I run into the issue. I added another parameter, lets just call it "Location". The parameter is a text data type that allows multiple values and gets it available values from dataset/query in the same report. This is where I am guessing what I want may not be possible. When I select my Location(s), then run the report it all looks good. However, when I click on one of the Expand/Collapse text boxes, it clears out the values that I selected for the location(s). I am guessing this is due to the fact that the available values for the Location parameter is set via a query at run time. Is there any way to maintain the values for the Location parameter when triggering the expand/collapse buttons?
Thanks in advance!
This question already has an answer here:
How to query combo box of only current record/row in Access data entry form?
(1 answer)
Closed 1 year ago.
I am trying to make a dependent drop down work with my database here but it is giving me a hard time for different reasons that I will explain.
This is what I have:
A form called "tblOTS" (split form based on an actual "tblOTS" table):
As well as a table called "tblAlphaCode":
When looking at the property sheet for the "Alpha Code" combobox (actually called "strOTSAlphaCode") on my tblOTS form, this is what I have:
The current SQL statement under "Row Source" for this strOTSAlphaCode is:
SELECT tblAlphaCode.strAlphaCode, tblAlphaCode.strCategory,
tblAlphaCode.ID, tblAlphaCode.numSortingOrder
FROM tblAlphaCode
ORDER BY tblAlphaCode.strCategory, tblAlphaCode.numSortingOrder;
Basically, when user select an Alpha code in the drop down from "tblOTS" form, it adds the ID of the tblAlphaCodes into the actual tblOTS record.
My goal is to have the user select first a "Category" (here FASTENERS/HARDWARE ...) when adding/modifying an OTS record, and then have the "Alpha Code" drop down dependent on what category was just selected.
I first tried to changed the SQL statement using a WHERE condition on the category field, based on the form category field itself:
SELECT tblAlphaCode.strAlphaCode, tblAlphaCode.strCategory, tblAlphaCode.ID, tblAlphaCode.numSortingOrder
FROM tblAlphaCode
WHERE (((tblAlphaCode.strCategory)=[Forms]![tblOTS]![strOTSCategory]))
ORDER BY tblAlphaCode.strCategory, tblAlphaCode.numSortingOrder;
And created a strOTSAlphaCode.requery in my Form_Current event to update it everytime.
However, it affects the whole form itself as my control source is directly affected by my Row Source in this instance, and the form looks like this:
You can see that the drop down is working beautifully, however, all the fields that do not have the same category as the current record that I work on (FASTENER <> HARDWARE here), are missing their Alpha code (the second record is missing "O-RING" compared to the first picture from this post); this behavior is problematic!
I tried to find workarounds by changing strOTSAlphaCode into a simple text box only containing the Alpha Code ID, added an unbound text box on top with dlookup function to find the actual alpha code related to this ID, and an unbound combobox in between with the exact same SQL statement inside the Row Source Property, that would update the strOTSAlphaCode with some VBA ... not ideal right?? Ahaha. This is why I believe there is a simpler way that I am not aware of, but also I would like to use a "search as you type" code for this combobox later on and this solution was making it very difficult.
How can I make this work? I believe the answer is a simple/different SQL statement to put in my Row Source property, that is probably something related to some type of JOIN statement? Or something else? I expect to write some VBA code to make all of this work flawlessly, but I want to make sure that I have the right SQL statement first.
Thank you June7;
Yes, the link you gave me ( this link ) states 2 solutions, and the second one is the one that I talked about when describing my problem:
for forms in Continuous or Datasheet view, include lookup table in form RecordSource, bind a textbox to descriptive field from lookup
table, position textbox on top of combobox, set textbox as Locked Yes
and TabStop No
So I guess, the answer is that I MUST have a textbox with dlookup setup for my case; I put it on "locked" so that if the user wants to change it by typing in it, he will first have to select the arrow. This will work with what I wanted to do
Cheers,
I have two fields on a form. Field 1 is auto number field named 5sID. Field 2 is a lookup field named 5sType.
When I open the VBA code for both the oncurrent and on open, I try to reference either field with a "Me.5sID" or "Me.5sType". In either case when I type in the "Me." the auto list shows the other eight fields in the table, but not these two.
I have used this for years on both datasheets or continuous forms. There are only the two fields on the form and they were selected from the table field list in the design view.
If I change the name on the Other tab of the property options, the fields then appear.
I have now rebuilt the table and the form, I have created a database and linked to the same table and still get the same results.
If I add another short text field it shows up when I type "Me." in VBA, but any other type of field does not show up.
Naming an identifier with a number as first character is a bad idea! Always start with a letter!
On Access 2013 that creates a compile error as the compiler expects a=as he interprets.5as a decimal-number.
That worked for you on older versions? Hard to believe!
As workaround use square-brackets like on identifiers containing spaces or other crap.
Me.[5sID]
or turn onShow hidden Elementsin Object-Browser , what fixes Inteli-Sense and creates automatic brackets. Seems like this is a way to create hidden members ;)
I am designing a report in IBM Cognos Report Studio 10.2.2 that includes a list of different types of disabilities and the count of employees that have each type of disability. However, this list is only supposed to display if there are at least 10 employees with some kind of disability.
I tried solving this problem by creating a separate query (Disability summary) with a data item (Disabled) where each employee gets a 1 if they have a disability and 0 otherwise. I then added another data item (Number disabled) that I define as:
total([Disabled]) for report
I then create a Boolean variable in the Condition Explorer (Disabilities Reportable) which I define as:
[Disability Summary].[Number disabled] >= 10
Next, for the list that displays the count for each type of disability, I set the Render Variable to Disabilities Reportable. I also place a singleton elsewhere on the report page and set the query to Disability Summary and check Number disabled as a property. I also insert the Number disabled data item in the singleton.
However, when I run the report, I get the following RSV-VAL-0032 error:
The following expression is not valid: [Disability Summary].[Number disabled] > = 10.
If the item exists in a query but is not referenced in the layout, add it to a property
list. CRX-API-0005 An error occurred at or near the position '0'. The variable named
'[Disability Summary].[Number disabled]' is invalid.
Render Variables need to be accessible to the Page where they are used. If it works in a Report Expression, it will work in a Render Variable.
This means you must use prompt variables, built in Report Functions, or the query that is tied directly to the Report Page.
Assign the query that you are pulling your disability count from to the Report Page, then set the disability count field as a 'Property'. This makes the field accessible to the report for formatting and Report Expressions.
Click anywhere in your report, then on the properties panel click the Up Arrow to drill up the the very top, the 'Page' level. (Alternatively, Page Explorer->Report Pages->Double Click the Page you are working on)
Define the 'Query' and 'Properties'.
Creating a separate summary query is perfectly acceptable. If your summary is at a different aggregate level than the details of your list, Cognos is going to create a separate query and make separate database trips anyway. Use whatever method works and makes sense for you.
I've got a form that's got a subform and THAT subform/child has a subform/grandchild.
When I add a new client to the main form, the subform/child contains data like shipping address, etc etc. The subform/grandchild that one contains data like what we're shipping them.
When I make my initial new entry in the top form, there's data that seems to auto populate into the subform/child (and subsequently the table), however there are things that are always "default" items to ship (third subform/grandchild) that do not do that.
I've got some table constraints for the grandchild table like (ShipPackingSlip type bit) is set to 1, so that the checkbox should always be true. However, this does not occur on the 3rd layer of the form. Even setting the default option value to -1 will "autocheck" the box, but the data behind the forum does not reflect that.
Am I doing something wrong here?
Does that even make sense?
As I understand it (and I could be wrong), you can't use a subform in a subform on a main form without problems. It's better to organize your data and forms so that if you need to view more detailed information on data presented in a subform - it's better to call a new form from a button on the subform, passing a value to it so it pulls the correct record to view.
This would, of course, require you to store this subform of the subform data in a related table - then just relate it back to the main database with a unique identifier. This allows you a bit better means to organize your data, indexing isn't a pain, and you don't repeat information entry as much.