Universe dictionary

[rcoop]

Hi,

I'm new to sb+ so go easy on me.

I'm working thru the 'SB+ Solutions' guide to assist with my exploration.  I'm at the point of developing a screen and I want to use an existing universe file.  How can I view the dictionary for an existing universe file.  It seems like the only dictionary items you can view are the one's created in sb+.

thx,

rudy

[precisonline]

You're right, the only dictionaries you can see are those created via SB+'s /FD tool.  However, there is a tool in SB+ called MAKE.SBDICT that will convert existing dictionaries to SB+ format.  MAKE.SBDICT doesn't make very pretty dictionaries but it can be enough to get started.  You'll still have to fill in the SB+ part, of course, validation, default, intuitive help, etc.  Also be sure to check your conversions after running MAKE.SBDICT.

[rcoop]

I have another question in regards to the UV dictionary.  I used MAKE.SBDICT like you suggested, and it worked fine.  I then was able to
edit my dictionary items in tools>field definitions.  After editing a few of the dictionary items I examined them and noticed they were changed from a D type to an A type and my sql data type in field 8 were gone.  So my question is, what is the common practice with others when using existing dictionaries?  Is a new subset created just for system builder?

thx,

rudy

[precisonline]

I don't know if there's a "common practice" as much as a variety of options depending on what you're really trying to achieve.  So with that in mind, here's some things to consider:

a) MAKE.SBDICT does only the minimum amount necessary to create the SB+ field definition.  As a result, what it creates in terms of derived values is usually pretty spartan and may not use SB+ as effectively as you might if you created the dictionary from scratch.

b) An SB+ enabled dictionary has a lot of fluff in it.  Each field that is converted gets a dot-prefixed item in the dictionary, so if NAME is the original field converted, the end result is a new record in the dictionary called .NAME that is for SB+ only.  Screen definitions and report definitions are also stored in the dictionary of a file with SB+.  Therefore, folks that came to SB+ with a clean dictionary are usually pretty chagrined to learn that SB+ doesn't keep a very clean house there.

c) I'm of the mindset that if there's a working application, leave its dictionaries alone.  Create a new file for your SB+ dictionaries because SB+ can reference split dictionary and data files easily.  This keeps the original files and dicts intact and clean, and then you have your separate SB+ space that is completely independent of the original application - though it can update the same files.

d) If there is no application, such as a demo system, then I wouldn't be so worried about hocking up the dictionary.

Just one opinion.

[DonQuixote]

If you just want to see existing dictionary items that have not been converted to SB+ then just go to TCL and type  LIST DICT filename.