LOGTEXT question

John Esak john at valar.com
Fri Nov 7 19:43:31 PST 2008


Now, I absolutley don't believe this.  Yet another example of Hodgkiess's
Law of Parallel Planetary Development....

I asked Ken today about LOGTEXT for a different reason... But I have never
used LOGTEXT before in all 29 years of Profile/FilePro development... Okay,
so maybe it's only been around for 20 of those years... But still, to have a
question about it pop up from two people when it hasn't been heard from for
whatever... It is one of those a bugs comes up in filePro, nobody has ever
noticed it, then it hits two people who don't talk to each other within
hours.... Doo-dee-doo-doo, doo-tee-doo-doo...

Anyway, I'll check if there is a 255 limit... Since it was meant to generate
a sinlgle line of text at a time... I guess 255 would be a reasonable
limit... On the thought that most folks would use up to 80 or even maybe 132
chars at most... And 255 is the limit for a dreport line as well.  Maybe all
factors played into choosing this number.  Obviously, this is not 20 years
ago, and all sorts of ideas come up for commands that were never in the eye
of the creator... And a higher number would have been better... What, maybe
1024??  You wouldn't want all 32,768 would you? :-)   I don't know,
something is telling me it isn't like an import buffer size or the like.  I
think this is a sort of WRITELINE() for dummies... (clearly not referring to
you Bob... :-)  and it was just pinched and packaged to do a quick job
quickly.  It comes under the "debugging" functions... So I guess its use was
seen as a shortcut for doing all the requisite file I/O... Another por man's
WRITELINE() is "jsfiles", but of course more designed for html usage...
Still I've seen people go to the trouble of using that instead of a create()
and writeline().  

Would WRITELIE() work in your context Bob? 

John
> -----Original Message-----
> From: filepro-list-bounces+john=valar.com at lists.celestial.com 
> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.co
m] On Behalf Of Robert Haussmann
> Sent: Friday, November 07, 2008 2:19 PM
> To: 'filePro Mailing List'
> Subject: LOGTEXT question
> 
> When using the LOGTEXT command in filePro 5.6.09R9 (Native ODBC), 
> logged entries seem to be truncated after 255 characters.  Is
> there any way (environmental variable?) to overcome this limitation?
> 
> Thanks,
> Bob Haussmann
> Tabor Children's Services Inc.
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 



More information about the Filepro-list mailing list