View Full Version : Adding new fields from tables
ivankaupa
26-Feb-2010, 01:23 PM
Hello,
I created a new field, but the VRW doesn't show this new field.
What should I do to update the table's definition inside my report (same as Verify Database from Crystal)?
Regards,
Ivan Kaupa
Vincent Oorsprong
27-Feb-2010, 03:56 AM
Ivan,
This feature has been planned for after release. Currently you would need to remove the table from the report and add it again, sorry.
PS: The good thing is that Visual Report Writer does not crash like Crystal Reports when the table structure changed.
ivankaupa
27-Feb-2010, 09:00 AM
Vincent,
I tried remove and add the table again. But doing it I lost all the field from this table on the Report. I need to put all the fields again.
I will be honest. It is not possible to use VRW in a production site without a "Verify Database" option. It is common to add new fields on reported tables. Or at least, do not remove the fields from report when I remove and add the table again on the Database Expert.
To me, its better wait more few weeks to VRW 1.0, but including this option.
Regards,
Ivan Kaupa
phvwijk
27-Feb-2010, 02:17 PM
Vincent,
Removing the table and adding it again is not a valid option. Would require a rebuild of all work done with that database table. In a complex report that would be to much.
In database development adding field, changing field attributes is something, well at least for me, frequently happening.
Peter H. van Wijk
X-Organize Consultancy N.V.
Samuel Pizarro
28-Feb-2010, 08:19 PM
Vincent..
I also agree with Ivan and Peter.
It's a complete waste of time beginning using this product right now without this feature.
If you have already a large complete products (workspaces), thats ok. But If you have a lot of workspaces been builded, structural changes occurs every time..
I have to wait too!
Regards
Samuel
Boris
2-Mar-2010, 02:25 PM
I agree with Ivan, Peter & Samuel.
And I'll also add a request: Make a function within VRW that scan ALL reports and do an automatic Verify Database like MassVerify does.
Same features as crystal and same problems? :(
Michael Mullan
2-Mar-2010, 02:51 PM
better yet make the runtime do it when the report is run. Crystal dos this, but won't save back the changes to the report file, so it "Fixes up the report" Every time it runs, instead of just the first time..
ivankaupa
2-Mar-2010, 05:46 PM
Boris,
It is a great idea, but don't you are thinking about this feature on the first VRW version. Do you?
It could be very hard-working to the DAE guys at this time. But a simple Verify Database is needful for me on the first VRW version.
It is my opinion. Without a Verify Database option I will not create new Report with VRW because I can lost my job if I need to add a field on the report.
Regards,
Ivan Kaupa
ivankaupa
2-Mar-2010, 05:47 PM
Michael,
Great idea too.
Regards,
Ivan kaupa
Boris
4-Mar-2010, 09:21 AM
I really don't think DAW with release the product without at least adding the Verify Database option. It is a daily requirement to add new fields to everyone of us. Deleting and readding a table as Vincent's suggested is not an option, because you'll loose all the fields in the report.
I think Vincent's suggestion is based on the fact that we're only testing the product. This feature is a MUST!!!
Maybe my request or Michael's request will come after the official release.
I'm very happy with DAW making a decision this big to write their own report writer. I've been asking it for years. And now that business objects is under SAP, the support is harder to get and I have always said that besides DAW's exceptional products, there is a great community of developers here.
ivankaupa
4-Mar-2010, 09:28 AM
Boris,
I agree.
I'm very happy with VRW too.
[]s
Ivan Kaupa
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.