I would like to add the terms to SO-C.  In SD-M I have Packing Slip format number 6.  Can I assume that since the  only available changes in edit RTM files is BKsoc1.rtm, BKsoc2.rtm, BKsoc3.rtm and BKsoc4.rtm that I can not make this change?  How do you add additional new info in change forms?

Quote from JNAPIER   on 02/05/07 at 11:57:14:

The only potentially time consuming part is trying to identify the field you want and then verify that the table is being opened by the print program. Other than that it is really very straight forward:
 
Click the DBText button.
Click on the form where you want it.
Double-click the empty space to the right of "DataField" in the right pane.
Select the table you need using the drop-down box.
Double-click the field you want.
Format and position precisely if desired.

I have a suggestion to propose to you the users...
 
We have (all be it, outdated) list of files and fields on our web site. If a group of users gets together and assigns modules to one another, then you the users could come up with an updated list of files and fields in a short time. Whatever  you are missing we could fill in. This would help out all the users  who are trying to do Crystal and/or RTM editing.  
 
The one on our web site took us a long time to get to where it is, but we have no one to maintain it, so it has become outdated.  
 
 
This is just a suggestion, but I think it would help you all.

While we're on the subject, a place for users to share their hacks (SQL, RTMs, Crystal Reports, Web programs, MS Queries, etc.) would be a good thing if policed at least as well as the rest of this board.

Getting a list of the fields is not too hard. Coming up with a description of the field is a bit more time consuming. Even more useful would be adding notes to fields like BKIC.MSTR.UOH saying "Sum of Location records (BKICLOC) and should agree with transaction register (INVTXN)", etc.

Yes, I'd still really like to see this too!
 
Quote from GasGiant   on 02/06/07 at 09:50:15:

We are working on a new Evo~ERP web site, that will have a place to share user programs like RTM's and Crystal and access or whatever.
 
 

I did some checking into this and I've got a question:
 
BTrieve (terrible as it is) still has support for putting a description to each field of each database file. This would allow the descriptions of fields to be stored right in the database itself so that in the screen and report editors the descriptions will pop up right along with all of the fields. So why don't we add the descriptions right in there rather than waste time with an external file? Wouldn't it make sense to store the descriptions right in where they'd be of the most use? Someone at DBA has already put some field descriptions in but very few are filled in.
 
All this and more can be yours now for the low, low price of.... FREE. All people have to do is download TAS7i from addsum to get the data manager. Or, ISTech could get permission to distribute wtasdmgr.rwn which is all that's needed to muck about with the file descriptors in Evo.

It would be difficult to do a search across the whole database for what you are looking for regardless. If you search for unit on hand you'll find it in 20 places and you'll still have to guess which one you really want. Also, unless we come up with a standard method of description you will be hard pressed to guess what someone has used as the description of a field. I would think that it would be much more valuable to have the information associated with the fields themselves in the database so that one could figure out what a field is when they need it most. That is, when they are building a report or screen. Even then, I could see the use for at least a list of the tables with descriptions in an external file so that looking up the right table to use is easier. On that note, it might be nice to get a list of which reports reference which tables. I would think that that would be the most important information to have external to the database.
 
Still, I don't mean to suggest that I'm opposed to having the info externally. It would certainly be good to have the info in both internal and external form. I wonder how easy it is to programatically insert the field descriptions into BTrieve. That way people could work on the descriptions in the excel file and then import them into the database. That way we've got it both ways.  
 
Quote from David Waldmann   on 02/07/07 at 04:48:01:

Quote from kkmfg   on 02/07/07 at 05:13:35:

 
Wouldn't the opposite be easier? Get the descriptions into the tables and then extract it into a table.  
 
The other point you bring up is key: having a list of what tables/fields are used for various reports and even screens in DBA/Evo would be... unlikely. Um, no, I mean that it would be extremely useful!

Count us in on the group effort to get it updated.  We desperately need it ourselves!
 
Val

Quote:

 
If the description fields were populated as suggested, it  would be just short of trivial to create a Crystal Report (or Access, Excel, anything that can access the database with ODBC ...)  to generate a flat text file for those that want it.  
 
This would allow us to separate the content (descriptions) from the presentation (database lookup, flat file).  Doing so keeps us from constantly trying to synchronize everything.  Doesn't it make sense to use a 'DATABASE' to document our databases