This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C1C02F.D5463AB0
Content-Type: text/plain;
	charset="iso-8859-1"

We,

Are just developing a brand new system in VB and Crystal.  Our Crystal
Reports expose a list of expose paramaters with a specified list of
parameters, eg vb_CustomerIDs/vb_EmployeeIDs, vb_ParamFieldOne etc etc

VB itterates through all of the available parameters finding the ones
prefixed with vb_*  The crystal reports expose detailed info for each
parameter, such as the name of the field, and SQL to provide lookup data (ie
for populating combo's) etc.  Using this method you can dynamically build up
your VB screen to accomodate each report.  

Our reports also contain a vb_SQL paramter which contains the main SQL.  We
use this SQL to execute a query on the database through our own data
services layer - we have no direct link from Crystal to the database, but
instead are passing in ADO recordsets.

Therefore, so long as you agree some parameter names & rules, you can create
a single VB interface that should handle 99.99% of you reports.


-----Original Message-----
From: OB [mailto:oby.atabansi@h...]
Sent: 27 February 2002 19:10
To: professional vb
Subject: [pro_vb] VB and Crystal Reports


I have a project that requires 40 different reports to be generated with 
it.  Most of the reports are similar in functionality and interface.  Any 
suggestions as to how to go about developing without having to create 40 
parameter screens for 40 reports?