-- Topica Digest --
        
        Fw: Newbie Question
        By [EMAIL PROTECTED]
        
        RE: Importing text files--follow Up
        By [EMAIL PROTECTED]
        
        Fusedoc best practices
        By [EMAIL PROTECTED]

------------------------------------------------------------

Date: Sun, 13 Oct 2002 09:47:13 -0400
From: "scott" <[EMAIL PROTECTED]>
Subject: Fw: Newbie Question


Thanks, Lee.

After walking away and coming back to it later I finally found the single
typo that had been eluding me: an ending parenthesis in the fbx_Layouts.cfm
file. The "lightbulb" finally went on!

Cheers,
Scott

----- Original Message -----
From: "Lee Borkman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, October 12, 2002 11:58 PM
Subject: Re: Newbie Question


> Hi Scott.
>
> Without seeing some code, I would suspect that your circuits definitions
in
> fbx_circuits are a little faulty.  The FB3 core is pretty sensitive to the
exact
> form of the circuits definitions, and a common symptom is that FB3 may
find the
> target circuit fine, but does not find the circuits coming back up (ie
where
> layouts are implemented).
>
> Any chance we could see your fbx_circuits code?
>
> Anyway, once you get this hiccup sorted, you'll be flying ;-)
>
> See ya,
> LeeBB
>
> ----- Original Message -----
> From: scott <[EMAIL PROTECTED]>
>
> Hi, I'm going through the Getting Started tutorial from the Fusebox.org
site and
> I can't figure out why the Layout files are not being displayed. Can
anyone give
> me a hint?
>
>
> __________________________________________/Fusebox Conference!
>
>  Sign up for the Fusebox Conference today!
>  October 26th & 27th: Orlando, FL, just before MACR DevCon.
>  2 jam-packed days, 15 speakers in three tracks, World Fuseball
>  Championship
>  http://www.fusebox.org/index.cfm?fuseaction=conference.main
>
>
>
>





------------------------------

Date: Mon, 14 Oct 2002 08:30:45 +0100
From: Dave Phipps <[EMAIL PROTECTED]>
Subject: RE: Importing text files--follow Up


Hi,

I'd like to take a look at that as well if possible as I have a fusebox app 
which will soon be needed to dump some data into a csv file to be imported 
into an offline access db.

Cheers

Dave Phipps


At 09:03 10/11/2002 -0400, you wrote:
>         With access the fastest way to do what you want is to create a 
> linked table in access to the csv file.  With this link you can then do a 
> append query
>
>INSERT INTO Table1 ( Field1 )
>SELECT [linktable].Field1 AS Expr1
>FROM [linktable];
>
>Just use cffile to write the uploaded file to the server then run the 
>append query.  This will be your fastest method and also the simplist with 
>code.  But will only work correctly if one person at a time uses it.  So I 
>recomend putting a CFLOCK around the cffile and query to prevent multiple 
>access problems.  If you want I can send you a access file with an example 
>of a linked file.  Email me off list if you would like one.
>
>Daniel D.
>
>-----Original Message-----
>From: Nev [mailto:[EMAIL PROTECTED]]
>Sent: Friday, October 11, 2002 1:05 AM
>To: [EMAIL PROTECTED]
>Subject: Re: Importing text files--follow Up
>
>
>Or if you're on cf5, try Patrick's 
><http://www.cflib.org/udf.cfm?ID=507>http://www.cflib.org/udf.cfm?ID=507
>
>Nev
>
> >>> [EMAIL PROTECTED] 10/11/02 12:37pm >>>
>The simplest, most mindless, workaround is to do a global replace before you
>parse the data.  Replace Tab-Tab with Tab-N/A-Tab or similar.  That will 
>let CF
>parse the data, and you just have to deal with the N/A fields after parsing.
>
>Apologies to all for the non-Fusebox topic.
>
>See ya later,
>LeeBB
>
>
>
>----- Original Message -----
>From: Terry Hogan <[EMAIL PROTECTED]>
>
>Yes, there are blank fields.  I think that's the problem.  How do I handle 
>them?
>
>*********** REPLY SEPARATOR  ***********
>
>On 10/11/2002 at 1:25 PM Lee Borkman wrote:
>
> >Hi Terry,
> >
> >Any blank fields in your tab-delimited file?  CF's list functions treat two
> >consecutive delimiters as a single delimiter.  In other words, if you have
> >blank
> >items, then the subsequent items get shunted forward and your list gets
> >shorter.
> >
> >just a thought.
>
>
>
>__________________________________________/Fusebox Conference!
>
>Sign up for the Fusebox Conference today!
>October 26th & 27th: Orlando, FL, just before MACR DevCon.
>2 jam-packed days, 15 speakers in three tracks, World Fuseball
>Championship
><http://www.fusebox.org/index.cfm?fuseaction=conference.main >http://www.fu 
>sebox.org/index.cfm?fuseaction=conference.main   --=_065A90AF.D0B1D230-- 
>------=_NextPartTM-000-615b9555-dccf-11d6-9544-00105a68c8ef-- 
>${list_footer} ${list_promo} ${list_footer} ${list_promo}
>
>
>
>__________________________________________/Fusebox Conference!
>
>  Sign up for the Fusebox Conference today!
>  October 26th & 27th: Orlando, FL, just before MACR DevCon.
>  2 jam-packed days, 15 speakers in three tracks, World Fuseball
>  Championship
> 
><http://www.fusebox.org/index.cfm?fuseaction=conference.main>http://www.fusebox.org/index.cfm?fuseaction=conference.main
> 
>
>${list_footer} ${list_promo}


============================================
Phipps CF Development
Oxford, Oxfordshire.
Telephone: +44(0)7718 896696
http://www.phipps-cf.co.uk
========================================

====



------------------------------

Date: Mon, 14 Oct 2002 00:33:12 -0700
From: "Bill Henderson" <[EMAIL PROTECTED]>
Subject: Fusedoc best practices


Hey all - 

After reading Nat and Jeff's book, and cruising through halhelms.com, I
am getting a little bit more anal about setting up my fusedocs, and I am
wondering what other developers are doing in these situations:

A) I have been putting my XFA structure in the <in> element of all the
fuses of my fuseaction. This includes the qry_ and act_ files that do
not use them. I am trying to be thorough, but is this overkill?

B) Are people using the assertions element to just outline conditional
logic that affects the entire fuse, or any conditional logic they come
up with as they are writing the fusedoc?

C) I am a one man shop, and I have taken to writing myself very detailed
note elements about anything that I come up with while writing the
fusedoc. I tend to have a lot of thoughts about the structure of the
fuse in the stage before I write it, and I end up with as many as 15
lines of notes. I am wondering what everybody else does after the fuse
is written. Do you delete these pearls, or leave them for future
generations? 

I am not looking for answers, per se, but rather what other people are
doing regarding these <sarcasm>heavy</sarcasm> topics.

Bill Henderson
[EMAIL PROTECTED]





------------------------------




__________________________________________/Fusebox Conference!

 Sign up for the Fusebox Conference today!                         
 October 26th & 27th: Orlando, FL, just before MACR DevCon.       
 2 jam-packed days, 15 speakers in three tracks, World Fuseball   
 Championship                                                   
 http://www.fusebox.org/index.cfm?fuseaction=conference.main   

End of [EMAIL PROTECTED] digest, issue 971


Reply via email to