What I was referring to was to output the string and not execute the end
result SQL. Create a temporary variable that holds a string that you
create, so that you capture the SQL that you would normally execute. At
that point, you put the variable to see how the SQL would have executed and
ana
Get the output of one iteration of the insert statement by outputting the
end result of the SQL. Take the SQL statement and execute it directly
against your DB. If the insert works fine, it may be how you handle
different data types.
If it continues to elude you and you are comfortable with s
Joel,
I usually create a variable to hold the value of the directory that I want
to exist.
ei. "c:\pathtofile\directoryIwanttocreate"
After I create the string, I have a common method in a a file CFC like this:
- Original Message -
From: "Joel Watson" <[EMAIL PROTECT
To not repopulate another query with a sub query or to QoQ the data, I tend
to:
select
*
from
tableName
#qRead.Addr_ID[i]#
Query objects can be referenced like arrays and thus you can loop or
paginate over the data set with predefined boundaries.
On 5/11/07,
Les,
What are you trying to achieve in the encryption? If you are trying to
encrypt a form submission, the data is still passed in plain text prior to
the action page. Unless the form submission process resides in a folder
that has SSL enabled on it, then you could be doing work for nothing.
On
Something like this may help you:
#dowStr# day of week #woy# #yr#
Your could easily make the cfswitch statement into a UDF called something
like DayOfWeekOrder.
On 5/9/07, Pete Ruckelshaus <[EMAIL PROTECTED]> wrote:
>
> I'm building an app wh
I would recommend using client variables if you want to persist data that
needs to be saved even if your session dies.
If there is no consideration for persistent variables then session is a
great place.
On 5/9/07, Stewart Turnbull <[EMAIL PROTECTED]> wrote:
>
> The application was originally bui
7 matches
Mail list logo
