RE: Extremely long session names with dashes

2006-12-11 Thread Bobby Hartsfield
eld http://acoderslife.com -Original Message- From: Will Tomlinson [mailto:[EMAIL PROTECTED] Sent: Monday, December 11, 2006 2:10 PM To: CF-Talk Subject: Re: Extremely long session names with dashes >So no one has any idea where these come from? Let me ask a more pertinent qu

Re: Extremely long session names with dashes

2006-12-11 Thread Will Tomlinson
>So no one has any idea where these come from? Let me ask a more pertinent question. What does it matter?? lol! I'll inform dave of this microshaft event so he can attend with you, and get all his free viruses er... I mean software! :) Will ~~

RE: Extremely long session names with dashes

2006-12-11 Thread Bobby Hartsfield
What version of CF? ..:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com -Original Message- From: Doug Brown [mailto:[EMAIL PROTECTED] Sent: Monday, December 11, 2006 12:56 PM To: CF-Talk Subject: Re: Extremely long session names with dashes Actually mine is pretty

Re: Extremely long session names with dashes

2006-12-11 Thread Doug Brown
..:.:.:.:.:.:.:.:.:.:.:. > Bobby Hartsfield > http://acoderslife.com > > > > > -Original Message- > From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 07, 2006 9:55 AM > To: CF-Talk > Subject: Extremely long session names with dashes > > I had

Re: Extremely long session names with dashes

2006-12-11 Thread Doug Brown
field" <[EMAIL PROTECTED]> To: "CF-Talk" Sent: Monday, December 11, 2006 10:23 AM Subject: RE: Extremely long session names with dashes > So no one has any idea where these come from? > > (No not the stork Will lol) > > Ps.. Will I hope you have a good paying pro

RE: Extremely long session names with dashes

2006-12-11 Thread Bobby Hartsfield
-Original Message- From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 9:55 AM To: CF-Talk Subject: Extremely long session names with dashes I had someone ask me a question today about an error message they were getting when trying to read a session. The name of the

RE: Extremely long session names with dashes

2006-12-07 Thread Bobby Hartsfield
Hartsfield http://acoderslife.com -Original Message- From: Will Tomlinson [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 12:25 PM To: CF-Talk Subject: Re: Extremely long session names with dashes >I am on CF6 and he is on CF7. Maybe it?s a new option? I don?t see

RE: Extremely long session names with dashes

2006-12-07 Thread Bobby Hartsfield
PM To: CF-Talk Subject: Re: Extremely long session names with dashes The difference seems to be the hyphen '-'; CF parses the part of the name after any hyphen as a separate variable. He probably needs to use the bracket notation for the structure key ["mydemoweb_1558129_973910d81ad1363

Re: Extremely long session names with dashes

2006-12-07 Thread Will Tomlinson
>I am on CF6 and he is on CF7. Maybe it?s a new option? I don?t see any >difference between the 2. Still just the same old "Use UUID for cftoken" Is this like, a question? Are you talking to yourself again? lol Will ~| Create

Re: Extremely long session names with dashes

2006-12-07 Thread David
.:.:.:.:.:.:.:.:. > Bobby Hartsfield > http://acoderslife.com > > > > > > -Original Message- > From: Bobby Hartsfield [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 07, 2006 9:55 AM > To: CF-Talk > Subject: Extremely long session names with dashes &g

RE: Extremely long session names with dashes

2006-12-07 Thread Bobby Hartsfield
TED] Sent: Thursday, December 07, 2006 9:55 AM To: CF-Talk Subject: Extremely long session names with dashes I had someone ask me a question today about an error message they were getting when trying to read a session. The name of the session was: mydemoweb_1558129_973910d81ad1363a-56F3C720

Extremely long session names with dashes

2006-12-07 Thread Bobby Hartsfield
I had someone ask me a question today about an error message they were getting when trying to read a session. The name of the session was: mydemoweb_1558129_973910d81ad1363a-56F3C720-DA19-CB22-E5857B8E076CF998 The error was: "56F3C720," is not a valid identifer name. Yes, that is how 'Identifie