Not sure what would happen if any other routine is 'writing' to that field, and is > 12 chars.
Â
Â
Bill J.
Â
Â
Bill J.
--- On Mon, 2/1/10, Steven Gotschall <sgotschall@...> wrote:
From: Steven Gotschall <sgotschall@...>
Subject: Re: [Vantage] 6.1 Data Dictionary
To: vantage@yahoogroups.com
Date: Monday, February 1, 2010, 5:24 PM
Â
I've changed the size on Progress fields before and nothing bad happened. I am not a Progress expert, but from what I understand, the field size is more for how ODBC interacts with Progress then anything else. If you do experience a problem, just change it back. Of course I would make a backup of the database before making the change just to be on the safe side.
____________ _________ _________ __
From: warren klug <pirateofthemagothy@ yahoo.com>
To: vantage@yahoogroups .com
Sent: Mon, February 1, 2010 3:47:32 PM
Subject: [Vantage] 6.1 Data Dictionary
Â
I am haveing problems pulling in one of the Part level VB fields Part.Character08 into Crystal and manipulating with some functions. Crystal keeps giving me a message related to "invalid blob or memo field" and I cannot do any manipulation of the field, but it can be displayed.  I had an interesting suggestion to change the field size in the data dictionary form char(1000) to Char(12). Support line told me this was okay to do and would not impact any current system programs. My programming days go back to RPG on an AS/400 and if I was to change a field size every program that used the file would have to be recompiled.Â
Â
Does anyone see any problems with changing the field size on a user defined VB field in the Part file?
Â
One additional quesiton. Has anyone created individual view of key tables to be used in reporting to help generate reports faster?
Â
Â
Thanks,
Warren Klug
Lion Brothers
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]