JWColby
jwcolby at colbyconsulting.com
Tue Dec 12 16:23:33 CST 2006
>Yup, but I prefer the hex version! LOL, yea, 34 sounds pretty good to me too. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of DJK(John) Robinson Sent: Tuesday, December 12, 2006 4:22 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] More on vbCr, vbLf, VbNewLine, and vbCrLf Thanks. Yup, but I prefer the hex version! J -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gary Kjos Sent: 12 December 2006 20:00 To: Access Developers discussion and problem solving Subject: Re: [AccessD] More on vbCr, vbLf, VbNewLine, and vbCrLf Happy Birthday John. 64 in Decimal years then? GK On 12/12/06, DJK(John) Robinson <djkr at msn.com> wrote: > Nostalgia time (nothing directly to do with VB, just that I'm 40 > today, and some of you youngsters need educating) ... > > Once upon a time, mechanical typewriters had a roller mounted on a > carriage. The carriage moved the roller horizontally along its axis, > taking the paper past the fixed character-at-a-time print position. > When the line of type was complete, the carriage had to be returned to > its start position and the roller rotated sightly, feeding the paper > up one line's depth. Telex machines, teleprinters and suchlike called > these functions Carriage Return and Line Feed, even after the carriage > stayed still and the print head moved instead. On some devices you > could use CR on its own to overprint the previous line. > > Some of these electromechanical devices had rules to be obeyed, such > as CR before LF, because CR took longer physically. (One I recall > needed CR-LF-CR, because the explosive force of the return after a > long line made the darn thing bounce off its stops.) > > That's why the compound character is always CRLF (not LFCR) though I > prefer NL or NewLine. But how these different codes are handled by > more recent languages and devices is another story, which is why this > ramble has wasted your time - sorry! But thanks for the excuse, > Susan. > > Oh, and that '40' is in hexadecimal of course. ;-) > > John > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan > Harkins > Sent: 12 December 2006 17:46 > To: 'Access Developers discussion and problem solving' > Subject: [AccessD] More on vbCr, vbLf, VbNewLine, and vbCrLf > > > I'm finding that the vbCr, vbLf, vbNewLine and vbCrLf constants all do > the same thing within message box text -- they all begin text at the > left margin on the next line. I'm printing the evaluated statement to > the Immediate window and find the same thing there -- they all push > the text to the left margin of the next line. I can't see a difference > between them. > > Susan H. > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- Gary Kjos garykjos at gmail.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com