Home DADE

DADE for MyDAC (CoreLab) [RB703/D7]

edited November 2004 in DADE
Hi everyone,

I'm using RB7.03 with MyDAC 3 and the DADE they provided

Everything works fine under Delphi6 but migrating on D7, I get some
strange problems.

If I update my tables structure. The changes won't reflect in the DADE
(even after a disconnection/reconnection). I have to delete the MyDAC
component then the DADE gets refreshed with the new structures.

I think I have to change something in the DADE CoreLab provided and I
think this newsgroup is the best place to get the answer quickly without
digging in the code.

Regards,

Etienne

Comments

  • edited November 2004

    I don't understand what you mean when you say that you updated the tables
    structure. Do you mean that you run the end-user application and create new
    folders and reports?

    If you are compiling the plug-in into a package, then you need to update the
    'Requires' clause so that it uses the RB packages suffixed with 77 rather
    than 76 (77 = RB 7 for D7).



    --
    Nard Moseley
    Digital Metaphors Corporation
    www.digital-metaphors.com



    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
  • edited November 2004
    nope ...

    I mean I added new columns to my tables.
    Then I disconnect then reconnect so I can have my tables refreshed.

    The tables are refreshed but the DADE isn't, that is, the new columns
    dont appear in the Data view of the DADE.

    Etienne

    Nard Moseley (Digital Metaphors) a écrit :
  • edited November 2004

    1. Once you create a dataview, the columns for that dataview are
    persistently defined and stored. The SQL generated for the dataview,
    likewise lists the columns explicity - it does not use Select * notatation.

    2. The Query tools lists the available tables and fields. These lists are
    either derived from asking the database server (see GetTableNames and
    GetFieldNames in the DADE plug-in) or they are read from the RB
    DataDictionary. Use of the DataDictionary is optional. It can be used to
    control which tables and fields are available to the end-user.





    --
    Nard Moseley
    Digital Metaphors Corporation
    www.digital-metaphors.com



    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
This discussion has been closed.