Hello, I am trying to create a command button in a (form style) Subform that generates an html preview report. Here is my problem. First of all, I need to be able to pull all the records from within a date range,  say 02/01/2018..02/28/2018, then I need it to generate a report with all the records between that date range (not specific to the record on the Main highest level form). But what happens is, when I press the button the report comes up blank. I then tried to create this same report button on the Main highest level form and targeted it towards the subform, same result, a blank report. Actually, the only time the report works perfectly is when I run it specifically from that application. As in, I opened up the Subform from the application menu in it's own tab, retrieve the records I want, then press the button. However, this does not work for me, I want to be able to run this report on the fly, from within the main application,  or rather, the main form. I do not want to have my boss have to open up this other form separately in another tab and have to figure out how to use it and what not. I want them to just be able to push a button like normal. Are there any solutions for this? I was thinking that I might need to run programming from within the report, like GetValues and create a string array or something, then somehow force those into the report, but I really have no idea at this point. As far as reports I only have three commands to work with and I'm not sure how to use those to make  it do what I want it to do. As usual, thank you for your time and support.

Awesome, thank you.

Instead of "!Work_Date=vDate", try this:
"!Work_Date=" + vDate

You should also not be using @XResultSetForm(). @XResultSetSearch() returns a handle to a Resultset, That is the handle you will want to be using as long as it is greater than or equal to 0.

-Ray

I just realized something though that might be the problem. I'm asking it to call from "Action.db". I'm actually working with the "Action.dsr" and the actual "Action.db" is on another computer with the Server and it is not even updated to have this "Work" subform yet. Could that possibly be a problem calling the code? And if so is there a work around to where I could test this out and make sure it works before reconciling the database? Otherwise, I'll have to reconcile it first then test it out and so on.

Unless you are running this on the same form that is calling this code, you will want to use the name of that form, rather than @layout.

The second argument is the full database name as PainoMan pointed out in post #6.

Another reason you may get a -1 is if you have application security set on this application, and either the XUsername and XPassword are not set or they are set but not to a valid login for this application.

-Ray

actiontech wrote on Feb 20^th, 2018 at 12:00am:


Did you remove all Application Security or all Security for those layouts? They are two separate things. Application Security includes the layout security. If you are still prompted for a username and password when opening the file, you still have Application Security.

A -1 is going to be caused by 4 things.
1: An incorrect path in argument 1.
2: The Application specified in argument 1 is locked.
3: The Application specified in argument 1 is password protected and the X Username and X Password in this file is not a valid login for that application.
4: The full Database name in argument 2 is wrong.

Since you are using @FN, we can eliminate 1 and 2. So that leaves 3 and 4. One of those is what is wrong.

The field referenced in argument 5(or any field reference after that in additional arguments) will only affect the records returned in that ResultSet. IE: If you spell a field name wrong or have improper retrieve criteria, your ResultSet handle will be greater than -1 but you will have 0 records in that ResultSet.

-Ray