Please help

rbuser

Our live environment is still using RB 6.03 as we were with D5 for ages.

We are now only using D7 but have just installed RB7 as this is the only
upgrade our budget holders have paid for thus far.

Anyway

We have an end user report solution that works fine with our own
FreportExplorer as described in the guides.

We have the following line in our form

FReportExplorer.PrintPreview(FListView.ItemName, FListView.ItemId);

It does not work in D7.

I noticed that the PrintPreview changed to use (itemName and iFolderID)

Has this changed since 6.03 or am I losing the plot.

If I change our code to use FolderID i can get the report to run.

I know we can fix this but just wanted to see what has changed.

Thanks guys

Mark

nardmoseley

This was a bug fix. It should have been FolderID all along. The only reason
it worked it in prior versions is that the ListView.ItemId erroneously
returned the folder id. We fixed both of those bugs in RB 7.x





--
Nard Moseley
Digital Metaphors Corporation
http://www.digital-metaphors.com

rbuser

Nard

Many thanks for that we thought we were going crazy....

So I take it we just need to change our code to use FolderID instead of
ItemID and we are back in business.

Can I ask one thing tho...

Would it not be easier to just use ItemID instead of a combination of
ReportName and Folder ID

Cheers

Mark

nardmoseley

I do not recall the specific decisions behind the current implementation,
that would have to be researched. In general we try to not to modify the
method signatures because it breaks code in use by customers.


--
Nard Moseley
Digital Metaphors Corporation
http://www.digital-metaphors.com

rbuser

Nard

Many thanks

I replaced the code and it all works apart from the error in my post
above..re the data dictionary.

I think I have cracked it now. Is this another new property?
UseTableOwnerName. If i set to false it will run OK

Mark

nardmoseley

UseTableOwnerName is not a new property. See the TppDataDictionary topic in
the online help for more information about this property.

UseTableOwnerName is normally set to False, unless you are using Oracle.

In prior versions there was a bug related to this feature. When we fixed the
bug, some customers who had erroneously set this property to true reported
issues. Setting the property correctly to False, should provide the correct
behavior.



--
Nard Moseley
Digital Metaphors Corporation
http://www.digital-metaphors.com