Hi all I work with DataVu a bit. The first trap I got caught on was skipping through the documentation and missing steps, double check the steps in installation.
A couple of things to check. 1. make sure the entry is correct in the UV.ACCOUNTS file. 2. This does not use ODBC, but it does use SQL. If SQL is not working on your account you need to follow this through first. 3. If linux is involved check if some other steps need to be added. There was some issue with Linux in the beta that I thought was resolved but you may have to install something. In the beta a lot of work was done to ensure that DataVu works with all dictionary types and including SB+ dictionaries. What many are doing is setting up a new account with remote pointers and restricted dictionaries pointing to the data account. You can set that account to be ideal flavour and have different dictionaries to the data account and avoid touching the live account for reporting purposes. You can do what you want to SQLise this account without touching the data account. There is a little perseverance to get DataVu up and working, but in comparison to the work required to get up COGNOS, Chrystal reports and other BI tools to talk to U2, this is an easier path. Remember also that DataVu talks to other RDBMS, which means that you stop the need for pushing data into some SQL Server for reporting purposes and you raise the status of U2 in management eyes reducing the threat of U2 being replaced in your organisation. Another issue to look at. It is easier to transform data to an appropriate format in U2 than trying to manipulate it at DataVu level. Build SQL queries that produce an appropriate array to put into the DataVu Objects, this will save you some frustration going forward. Regards David Jordan _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
