Home End User
New Blog Posts: Merging Reports - Part 1 and Part 2

Datadictionary with ADO

edited September 2006 in End User
Hi,
I'm trying to work with the end-user designer & SQL Server 2000. I've
got the dictionary working to the degree that I can pull it up at
runtime via this code:

var
lForm: TdaDataDictionaryBuilderForm;

begin
lForm := TdaDataDictionaryBuilderForm.Create(Application);
lForm.DataDictionary := ppDataDictionary1;

if lForm.ValidSettings then
lForm.ShowModal
else
ShowMessage(lForm.ErrorMessage);

lForm.Free;


That tells me I have the data dictionary setup correct - it accesses
my tables no problem.

However, no matter what I do I can't get the dictionary to actually
have any affect. I've got it attached to the designer and
usedatadictionary set to true. I've made sure the sessions &
database name are correct. I'm assuming it's got somethign to do with
linking - i.e. the table name is probably not matching up. So, my
first question is how does it derive the table name when doing the
data dictionary matching? Also, how would I use a the results of a
query with the dictionary? I see there's an alias for everything, so
I could easily write my own routines, I'd just prefer not to.

Regards,
Nick Hustak

Comments

  • edited September 2006
    Hi Nick,

    The datadictionary was not designed to be used at runtime. The
    DataDictionary is typically used at designtime to define/filter the names of
    the tables, fields and automatic joins the end user will see while creating
    queries in DADE. What exactly are you trying to accomplish with your
    application?

    --
    Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
This discussion has been closed.