dbTalk Databases Forums  

mvBASE: Restricted length in calculated field?

comp.databases.pick comp.databases.pick


Discuss mvBASE: Restricted length in calculated field? in the comp.databases.pick forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Brian Speirs
 
Posts: n/a

Default mvBASE: Restricted length in calculated field? - 05-17-2005 , 04:57 AM






Hi,

I've got an interesting problem with an Info/Access dictionary item. The
dictionary looks up a value from a second file and concatenates it to
the key into the second file.

On output of the resulting value, the output gets truncated at character 48.

NOTE: This is happening when breaking on the value - not when being
output in a simple list.

I can't find any reference to this type of truncation in the
documentation. Has anyone else experienced this?

Dictionary item:

001 S
002 1
003 HS Code & Description
004
005
006
007 ML
008 A; (1):": "1)(THS10;X;;3)
009 T
010 55

File HS10

ID = 5101.29.00.02
Attr 1 = Very long description
Attr 2 = KGM
Attr 3 = Clean wool: not shorn < 24.5 microns

Output from dictionary item:

5101.29.00.02: Clean wool: not shorn< 24.5 micr

Does anyone have any ideas?

Thanks,

Brian Speirs
brian dot speirs2 at meat and wool nz dot com
--
************************************************** *
Brian Speirs
h: (04) 479 9032 c: (021) 265 5906
e: bss59REMOVETHIS (AT) paradise (DOT) net.nz

Reply With Quote
  #2  
Old   
Mecki
 
Posts: n/a

Default Re: mvBASE: Restricted length in calculated field? - 05-17-2005 , 05:14 AM






Hi Brian,

your problem has something to do with the space available for output.
This isn't necessarily related to the dictionary of the breaking value
but on the other dictionaries if you total or break on them.
Sometimes you have to change the order of the columns to display the
full breaking value.


Mecki

Brian Speirs wrote:
Quote:
Hi,

I've got an interesting problem with an Info/Access dictionary item. The
dictionary looks up a value from a second file and concatenates it to
the key into the second file.

On output of the resulting value, the output gets truncated at character
48.

NOTE: This is happening when breaking on the value - not when being
output in a simple list.

I can't find any reference to this type of truncation in the
documentation. Has anyone else experienced this?

Dictionary item:

001 S
002 1
003 HS Code & Description
004
005
006
007 ML
008 A; (1):": "1)(THS10;X;;3)
009 T
010 55

File HS10

ID = 5101.29.00.02
Attr 1 = Very long description
Attr 2 = KGM
Attr 3 = Clean wool: not shorn < 24.5 microns

Output from dictionary item:

5101.29.00.02: Clean wool: not shorn< 24.5 micr

Does anyone have any ideas?

Thanks,

Brian Speirs
brian dot speirs2 at meat and wool nz dot com


Reply With Quote
  #3  
Old   
news.xmission.com
 
Posts: n/a

Default Re: mvBASE: Restricted length in calculated field? - 05-17-2005 , 11:14 AM



On Microdata systems, for the longest time, the break-on values were limited
to 24 characters. Feel lucky you got 48!

Ed

"Brian Speirs" <bss59REMOVE_THIS (AT) paradise (DOT) net.nz> wrote

Quote:
Hi,

I've got an interesting problem with an Info/Access dictionary item. The
dictionary looks up a value from a second file and concatenates it to the
key into the second file.

On output of the resulting value, the output gets truncated at character
48.

NOTE: This is happening when breaking on the value - not when being output
in a simple list.

I can't find any reference to this type of truncation in the
documentation. Has anyone else experienced this?

Dictionary item:

001 S
002 1
003 HS Code & Description
004
005
006
007 ML
008 A; (1):": "1)(THS10;X;;3)
009 T
010 55

File HS10

ID = 5101.29.00.02
Attr 1 = Very long description
Attr 2 = KGM
Attr 3 = Clean wool: not shorn < 24.5 microns

Output from dictionary item:

5101.29.00.02: Clean wool: not shorn< 24.5 micr

Does anyone have any ideas?

Thanks,

Brian Speirs
brian dot speirs2 at meat and wool nz dot com
--
************************************************** *
Brian Speirs
h: (04) 479 9032 c: (021) 265 5906
e: bss59REMOVETHIS (AT) paradise (DOT) net.nz



Reply With Quote
  #4  
Old   
Brian Speirs
 
Posts: n/a

Default Re: mvBASE: Restricted length in calculated field? - 05-18-2005 , 04:37 AM



Thanks for the info. We'll see what work-arounds we can come up with.

Brian

Mecki wrote:
Quote:
Hi Brian,

your problem has something to do with the space available for output.
This isn't necessarily related to the dictionary of the breaking value
but on the other dictionaries if you total or break on them.
Sometimes you have to change the order of the columns to display the
full breaking value.


Mecki

Brian Speirs wrote:

Hi,

I've got an interesting problem with an Info/Access dictionary item.
The dictionary looks up a value from a second file and concatenates it
to the key into the second file.

On output of the resulting value, the output gets truncated at
character 48.

NOTE: This is happening when breaking on the value - not when being
output in a simple list.

I can't find any reference to this type of truncation in the
documentation. Has anyone else experienced this?

Dictionary item:

001 S
002 1
003 HS Code & Description
004
005
006
007 ML
008 A; (1):": "1)(THS10;X;;3)
009 T
010 55

File HS10

ID = 5101.29.00.02
Attr 1 = Very long description
Attr 2 = KGM
Attr 3 = Clean wool: not shorn < 24.5 microns

Output from dictionary item:

5101.29.00.02: Clean wool: not shorn< 24.5 micr

Does anyone have any ideas?

Thanks,

Brian Speirs
brian dot speirs2 at meat and wool nz dot com


--
************************************************** *
Brian Speirs
h: (04) 479 9032 c: (021) 265 5906
e: bss59REMOVETHIS (AT) paradise (DOT) net.nz


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.