ADDA FAQ There are numerous packages like ADDA which offer automatic upgrades, why should I use yours?    Our database upgrades are versionless. To go, for example, from version 1 to 10, usually long scripts must be run or manual selection is involved. A simple unsophisticated user can have a difficult time accomplishing this. ADDA analyzes the user's database structure and makes essential changes running differential queries. Re-distribution is easy and simple; no writing to registry or other Windows-specific operations are involved so you can include it in your setup or patching utility. Another distinctive advantage is the full support of end-user's database customization (Enterprise version). Are there any limitations in synchronizing that I should be aware of?    In the demo version the synchronizer has the same limitations as the data designers. Naturally, the full commercial version is unrestricted. How do I start working with ADDA?    After you install the package (which I believe you already did), open Dictionary Designer for the developer. If you have a database to start from, select Database->Import All from Database from the main menu. Please check "Allow saving password" or "Use Windows NT integrated security" for proper operation. Edit the dictionary as needed, then save it under name DICT.XML. Distribute it to your users with the Database Synchronizer package. When making changes to DICT.XML, re-distribute it to the users along with the updated version (simply overwrite the old copy). Does the synchronizer remove tables that are not part of the exported XML data dictionary?    No, it doesn't. It only deals with its own entities. Even with the user doesn't create his own tables, it would be highly dangerous, since MS SQL Server sometimes marks its tables as user's tables. However, all the triggers and indices used by an ADDA-monitored table, should be registered in the dictionary. This is because the table can be recreated, and then the linked entities are recreated as well. You might also want to check our unique feature that allows user-side customization and automatic upgrade ("Dictionary Designer - End User"). Does the synchronizer maintain table relationships?    Depends on how it is implemented. If you're doing it by setting up triggers, then it does. When the Synchronizer adds or removes fields from a table, is there any data loss? Meaning that it modifies the structure, rather than recreate the table.    Never, unless there is some kind of malfunction. That's the purpose of ADDA. You can take a look at the queries it creates; you can see that the synchronizer goes quite a long way to preserve the data. What do I need to redistribute to the end user?    Database Synchronizer and, optionally, Dictionary Designer for end users if you want to allow customization of the users' databases. There is a sub-directory named Redistribute under the root folder of the application. It contains a Setup utility and the same pack of files as they are under sub-directory named Raw, in case you want to distribute them in your package. In the enterprise edition of ADDA there are two options: to supply Database Synchronizer only or both Database Synchronizer and Dictionary Designer for end users. The provided installation utility contains a selection screen. I cannot connect to my database! I get exceptions saying the system is unable to logon?    When defining connection in the Data Link dialogue, please check "Allow saving password" or "Use Windows NT integrated security". There is a problem resolving this for now. I closed Dictionary FieldBox by clicking on X button. How do I reactivate it?    Simple. Select Tools -> Add-in Manager from the Visual Studio menu; make sure Dictionary FieldBox is checked for use and press OK. A message box will ask you whether you want to reactivate the FieldBox. Answer Yes. What ADDA stands for?    ADDA stands for Advanced Data Dictionary Architect. I develop in Delphi / C# Builder / other non-MS .NET tool. Can I use ADDA? Yes you can. However, you won't be able to use FieldBox add-in for MS Visual Studio ©. ADDA sounds great, but I use Oracle / MySQL / PostgreSQL / whatever. Do you support this backend? Not currently, however, it certainly is within the scope of our design. That's why we have this driver selection combo. Once we implement it, you'll be able to switch to it on-the-fly with the automatic redefinition of all the field types. However, cross-database automatic upgrades are questionable. I liked your length entry control. Where does it come from? I'm so glad you've asked:. It is our homebrew masked edit control. It enables convenient fool-proof data entry of numbers, patterns, dates, time and forcing input language and configures itself according to the selected mode. Except for Entry, we also have a bulk lookup control, data grid with smart paging mechanism loading small portions of the table, automatic update form, and lots of other possibilities. Be advised that we are going to release it all in a separate package.

Copyright ©2003-2005 Power-Component.net. All rights reserved. Privacy Policy Microsoft, Visual Studio, Visual Studio.NET, and the Visual Studio logo are registered trademarks of trademarks of Microsoft Corporation in the United States and/or other countries. Other product and company names herein may be the trademarks of their respective owners.