Jim,
We understand exactly your challenge. While Reporting packages like Crystal
and Safari provide excellent function in displaying the data, they are very
constrained regarding the ability to use native routines, saved-lists, etc.
The ODBC interface is not MV friendly. Our Informer Web Reporti
Jim Bullock wrote:
>
> Funny you should mention it. We just started experimenting
> with XML yesterday. CR comes with an
> ODBC driver for XML files. UD's LISTTOXML seems to work
> as advertised. Many details remain
> to be investigated, but it looks promising so far.
>
If LIST...TOXML
Funny you should mention it. We just started experimenting with XML yesterday.
CR comes with an
ODBC driver for XML files. UD's LISTTOXML seems to work as advertised.
Many details remain
to be investigated, but it looks promising so far.
Jim
--- John Jenkins <[EMAIL PROTECTED]> wrote:
>
I seem to remember there is a link into ADO for CR ... maybe you could link
into RBOs?
XML might be another possible methodology - but I don't have a copy of CR to
play with...
Anyone got any inside information on these features in CR?
Regards
JayJay
We have racked our brains and have been u
There are a couple of ways around that: you can use a different file for each
user or you can put some sort of identifier in the key for each user.
We did find some neat functionality in Crystal that meant we could use multiple
data files with one report. I forget what their terminology for it w
access to selected records in a file
To expand on Colins idea of a work file:
What about creating a process which can be passed a list of column
definitions (title,width,datatype, etc) and a set of report data
thenand creates an ODBC enabled work file which could be accessed by
crystal reports
Thank you both for the workfile suggestion. We have toyed a bit with this
idea. One of the
challenges we face is that we have 200 users who can run reports via the Web
and the Crystal
Enterprise reporting engine. Two simultaneous users couldn't use a single
workfile
simultaneously. We haven'
To expand on Colins idea of a work file:
What about creating a process which can be passed a list of column definitions
(title,width,datatype, etc) and a set of report data thenand creates an ODBC
enabled work file which could be accessed by crystal reports with a simple
"SELECT * FROM" SQL st
Thanks, Ross. Actually when we were looking for our reporting solution a
couple of years ago we
looked at the available 'native' U2 products and, for various reasons, decided
against them in
favor of Crystal Enterprise. Your reference to "The Drumheller Trick" sent me
Googling, but also
set th
Sorry, I haven't played much with our Crystal reports, but I think we had a
similar problem. However, we didn't have the large library of paragraphs that
we felt compelled to re-use.
I didn't think it was all that slow. We did figure out how to do some neat
things with Crystal though.
What abo
I've found the best way for me to do what you are describing is to use
UniObjects .Net to create a recordset from the UniData/UniVerse
machine and then pass that recordset into a Crystal Report. Probably
not what you want to hear, but it is a method to stitch together your
current programs with yo
Does UV SQL CALL syntax work for UD too? Can that be used to return the
rows you need from basic or a paragraph?
Stuart
-Original Message-
From: Jim Bullock
The natural, or so I thought, place to do this sort of thing is in a stored
procedure. I got as
far as "seeing" the stored pr
Jim,
Probably way to late in the day, but there are a number of non-ODBC/OleDB
solutions that might have solved this problem for you. Names like mvQuery,
Informer, and our own Visage.Reporter come to mind.
I assume the other products have something similar to our facility where you
can CAL
driven formatting, scheduling and a
number of other features.
Regards
David Jordan
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Craig Bennett
Sent: Tuesday, 15 March 2005 10:08 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] UD: ODBC/OleDB access to
in the ODBC/OleDB interface to UniData. Before we give up entirely and resign
ourselves to
putting out paper reports with UniQuery, I thought I would ask this group if
anyone has solved
this problem. Anyone?
Don't do that Jim. I you have to use UniQuery, at least convert the text
reports to PD
15 matches
Mail list logo