Paradox Community

Items in pnews.paradox-development

Subject:Re: formatted memo fields
Date:Wed, 3 Nov 2021 14:32:55 -0700
From:Peter <peterspammenot@whiteknight.email>
Newsgroups:pnews.paradox-development
I have a table that has 256 fields, 32 are F1. 6 F1 fields are at the 
end but the others are strewn throughout the table in no particular 
strategy.
Been working for over 20 years, had a minor issue once and has never 
caused any problems since. Customer hammers those fields pretty good 
too, using every conceivable formatting option possible.

I realized some time ago it was not the right way to do things but the 
point is that the table has 32 F1 fields and works fine.

I also read somewhere that if you are going to use FM / M fields then to 
put them at the end of table.


Peter


On 11/03/2021 10:09 a.m., Steve Green wrote:
> 
> yeah, I know.. avoid at all costs.. however, for this project, there are 
> a few that I can't eliminate right now
> 
> all are F240 in the tables, most are really several K in the memo file.. 
> all are problematic.. "formatted memo header" errors are common
> 
> the actual content is basically a small Word or Wordpad doc.. a font, 
> some bullet points, usually some bold
> 
> question.. from experience, if any, more stability if the base field in 
> the table holds as much as possible, like the F240, or more stability if 
> the base field in the table is just a small F10, or even F1? or does it 
> not matter?
> 
> 


Copyright © 2004 thedbcommunity.com