RonB
|
| Posted: 08/30/2002, 12:59 AM |
|
Hy, we've seen the editable grid. What i could realy use, and in theory
shouldn't be all that difficult, is an insertable grid. This way the user
can fill in, let's say a travel expense form, without having to submit each
and every record. He could fill in 1 month's worth of expensi declaration
and then submit the thing in one go. Anybody got any idea's on how to do
this?
RonB
|
|
|
 |
Shawn Mason
|
| Posted: 08/30/2002, 9:00 AM |
|
Hmm, that one does require a little thought. One one form I have I am
submitting value for mulitple tables and when submitted, parsing out each
tables values and issuing the Sql Insert (all handcoded of course). I guess
you could do the same with each individual record where you would parse out
the first records values from the submit, insert it, go to the next, insert
it, until you run out of values or reach whatever the maximum records you
placed. Not what I would call "elegant" but it's a start.
--
Kindest Regards,
Shawn Mason,CCD,MCP
I.S. Software Design Associates
"RonB" <r.borkent@123chello.456nl> wrote in message
news:akn8k6$md2$1@news.codecharge.com...
> Hy, we've seen the editable grid. What i could realy use, and in theory
> shouldn't be all that difficult, is an insertable grid. This way the user
> can fill in, let's say a travel expense form, without having to submit
each
> and every record. He could fill in 1 month's worth of expensi declaration
> and then submit the thing in one go. Anybody got any idea's on how to do
> this?
>
> RonB
>
>
|
|
|
|
Chip Cotton
|
| Posted: 08/30/2002, 9:37 AM |
|
Of course, this would be an easier question to answer if you indicated
language and database.
I use PHP w/MySQL, but this would work with anything, I'm thinking:
The grid would have a given number of rows, each row consisting of
various fields.
Produce this grid manually. I'd name each control with a prefix for
the row and a suffix for the field example:
r01_account_id,r01_desc,01,r01_amount,
r02_account_id,r02_desc,01,r02_amount...
You could end up with a lot of fields!!!
Then, I'd create a page which, upon posting, would loop through the
fields of the grid. Upon reaching the last field (amount here)
everytime, the insert statement would be added to an SQL statement
string which could then be fed to the database at one shot.
Further handling could include a field (next to the submit button)
which would indicate the number of rows. This would help simplify the
processing and error handling to help distinguish between a missing
required field and the end of the data.
Looking at this, I realize you may have to go 'outside of the box'
that Codecharge puts you in, perhaps someone can outline where this
processing could be put into the CCS paragim. It would be simple
enough to do in a straight up PHP page...
ALTERNATIVELY, YOU COULD CREATE a table of 255 fields to be appended
at one shot, then create some post-post processing program. This
latter approach WOULD take advange of CCS's data validation
capabilities.
CHEAP SHOT DEPT:
In the past, (and currently) to get things done, I've had to go
outside the box (create a page in the web outside of codecharge
studio), while I wait for Codecharge Studio to get its documentation
unified to explain all->of->its-> functions-> with-> *full*->
examples-> of-> each->for->each->language(). As it is, we're expected
to tool through x number of examples which do not pertain to our own
use, documentation void of examples, online forums that lacks full
text searching with every language mixed in together and of course,
this forum of loyal supporters.
On Fri, 30 Aug 2002 09:59:57 +0200, "RonB" <r.borkent@123chello.456nl>
wrote:
>Hy, we've seen the editable grid. What i could realy use, and in theory
>shouldn't be all that difficult, is an insertable grid. This way the user
>can fill in, let's say a travel expense form, without having to submit each
>and every record. He could fill in 1 month's worth of expensi declaration
>and then submit the thing in one go. Anybody got any idea's on how to do
>this?
>
>RonB
>
|
|
|
|
RonB
|
| Posted: 08/30/2002, 10:29 AM |
|
Hi Chip,
I know what you mean, I have the same complaints. The problem for me is that
in my department I'm the only one who knows how to do php/mysql and CCS.
This means that doing stuf outside of CCS will cause a lot of trouble if I
should change jobs and the next poor guy has to take over my job. By keeping
everything inside CCS it is a lot easier to maintain the intranet and get
some serious and usable documentation of what Im doing where and why.
The fact that php documentation is as poor as it is only makes it even more
important that I document what I'm doing.
"Chip Cotton" <please.no.email@Jail-Spammers.com> schreef in bericht
news:ci6vmuksu7pea849667islqhq9k29d0gcn@4ax.com...
> Of course, this would be an easier question to answer if you indicated
> language and database.
>
> I use PHP w/MySQL, but this would work with anything, I'm thinking:
>
> The grid would have a given number of rows, each row consisting of
> various fields.
>
> Produce this grid manually. I'd name each control with a prefix for
> the row and a suffix for the field example:
>
> r01_account_id,r01_desc,01,r01_amount,
> r02_account_id,r02_desc,01,r02_amount...
>
> You could end up with a lot of fields!!!
>
> Then, I'd create a page which, upon posting, would loop through the
> fields of the grid. Upon reaching the last field (amount here)
> everytime, the insert statement would be added to an SQL statement
> string which could then be fed to the database at one shot.
>
> Further handling could include a field (next to the submit button)
> which would indicate the number of rows. This would help simplify the
> processing and error handling to help distinguish between a missing
> required field and the end of the data.
>
> Looking at this, I realize you may have to go 'outside of the box'
> that Codecharge puts you in, perhaps someone can outline where this
> processing could be put into the CCS paragim. It would be simple
> enough to do in a straight up PHP page...
>
> ALTERNATIVELY, YOU COULD CREATE a table of 255 fields to be appended
> at one shot, then create some post-post processing program. This
> latter approach WOULD take advange of CCS's data validation
> capabilities.
>
> CHEAP SHOT DEPT:
> In the past, (and currently) to get things done, I've had to go
> outside the box (create a page in the web outside of codecharge
> studio), while I wait for Codecharge Studio to get its documentation
> unified to explain all->of->its-> functions-> with-> *full*->
> examples-> of-> each->for->each->language(). As it is, we're expected
> to tool through x number of examples which do not pertain to our own
> use, documentation void of examples, online forums that lacks full
> text searching with every language mixed in together and of course,
> this forum of loyal supporters.
>
> On Fri, 30 Aug 2002 09:59:57 +0200, "RonB" <r.borkent@123chello.456nl>
> wrote:
>
> >Hy, we've seen the editable grid. What i could realy use, and in theory
> >shouldn't be all that difficult, is an insertable grid. This way the user
> >can fill in, let's say a travel expense form, without having to submit
each
> >and every record. He could fill in 1 month's worth of expensi
declaration
> >and then submit the thing in one go. Anybody got any idea's on how to do
> >this?
> >
> >RonB
> >
>
|
|
|
|
Val Raemaekers
|
| Posted: 08/31/2002, 4:26 AM |
|
Hi Ron,
IF you think the PHP documentation is poor, I have one question for Yes
Software ::
WHERE IS THE COLDFUSION DOCUMENTATION ??? <G>
Val
"RonB" <r.borkent@123chello.456nl> wrote in message
news:akoa1i$j91$1@news.codecharge.com...
> Hi Chip,
>
> I know what you mean, I have the same complaints. The problem for me is
that
> in my department I'm the only one who knows how to do php/mysql and CCS.
> This means that doing stuf outside of CCS will cause a lot of trouble if I
> should change jobs and the next poor guy has to take over my job. By
keeping
> everything inside CCS it is a lot easier to maintain the intranet and get
> some serious and usable documentation of what Im doing where and why.
> The fact that php documentation is as poor as it is only makes it even
more
> important that I document what I'm doing.
>
> "Chip Cotton" <please.no.email@Jail-Spammers.com> schreef in bericht
>news:ci6vmuksu7pea849667islqhq9k29d0gcn@4ax.com...
> > Of course, this would be an easier question to answer if you indicated
> > language and database.
> >
> > I use PHP w/MySQL, but this would work with anything, I'm thinking:
> >
> > The grid would have a given number of rows, each row consisting of
> > various fields.
> >
> > Produce this grid manually. I'd name each control with a prefix for
> > the row and a suffix for the field example:
> >
> > r01_account_id,r01_desc,01,r01_amount,
> > r02_account_id,r02_desc,01,r02_amount...
> >
> > You could end up with a lot of fields!!!
> >
> > Then, I'd create a page which, upon posting, would loop through the
> > fields of the grid. Upon reaching the last field (amount here)
> > everytime, the insert statement would be added to an SQL statement
> > string which could then be fed to the database at one shot.
> >
> > Further handling could include a field (next to the submit button)
> > which would indicate the number of rows. This would help simplify the
> > processing and error handling to help distinguish between a missing
> > required field and the end of the data.
> >
> > Looking at this, I realize you may have to go 'outside of the box'
> > that Codecharge puts you in, perhaps someone can outline where this
> > processing could be put into the CCS paragim. It would be simple
> > enough to do in a straight up PHP page...
> >
> > ALTERNATIVELY, YOU COULD CREATE a table of 255 fields to be appended
> > at one shot, then create some post-post processing program. This
> > latter approach WOULD take advange of CCS's data validation
> > capabilities.
> >
> > CHEAP SHOT DEPT:
> > In the past, (and currently) to get things done, I've had to go
> > outside the box (create a page in the web outside of codecharge
> > studio), while I wait for Codecharge Studio to get its documentation
> > unified to explain all->of->its-> functions-> with-> *full*->
> > examples-> of-> each->for->each->language(). As it is, we're expected
> > to tool through x number of examples which do not pertain to our own
> > use, documentation void of examples, online forums that lacks full
> > text searching with every language mixed in together and of course,
> > this forum of loyal supporters.
> >
> > On Fri, 30 Aug 2002 09:59:57 +0200, "RonB" <r.borkent@123chello.456nl>
> > wrote:
> >
> > >Hy, we've seen the editable grid. What i could realy use, and in theory
> > >shouldn't be all that difficult, is an insertable grid. This way the
user
> > >can fill in, let's say a travel expense form, without having to submit
> each
> > >and every record. He could fill in 1 month's worth of expensi
> declaration
> > >and then submit the thing in one go. Anybody got any idea's on how to
do
> > >this?
> > >
> > >RonB
> > >
> >
>
>
|
|
|
|
Carl
|
| Posted: 08/31/2002, 5:59 AM |
|
FYI:
ColdFusion Documentation is very extensive. When you install it it's under
http://installedhost/cfdocs/ . It covers every CF Tag, has sample code and
much more. It also comes with sample databases and working examples.
Carl
"Val Raemaekers" <val@valtronics.co.za> wrote in message
news:akq94h$vqa$1@news.codecharge.com...
> Hi Ron,
> IF you think the PHP documentation is poor, I have one question for Yes
> Software ::
> WHERE IS THE COLDFUSION DOCUMENTATION ??? <G>
> Val
>
|
|
|
|
Val Raemaekers
|
| Posted: 08/31/2002, 10:52 AM |
|
Hi Carl,
I am well aware about the documentation that is shipped with coldfusion
itself.
The documentation I am after is a codecharge programming reference for
coldfusion as is provided in the helpfiles that ship with codecharge for asp
and php ...
Val
"Carl" <herrecm@itis.net> wrote in message
news:akqej6$a9e$1@news.codecharge.com...
> FYI:
>
> ColdFusion Documentation is very extensive. When you install it it's
under
> http://installedhost/cfdocs/ . It covers every CF Tag, has sample code
and
> much more. It also comes with sample databases and working examples.
>
> Carl
>
> "Val Raemaekers" <val@valtronics.co.za> wrote in message
>news:akq94h$vqa$1@news.codecharge.com...
> > Hi Ron,
> > IF you think the PHP documentation is poor, I have one question for Yes
> > Software ::
> > WHERE IS THE COLDFUSION DOCUMENTATION ??? <G>
> > Val
> >
>
>
>
|
|
|
|
Carl
|
| Posted: 08/31/2002, 3:58 PM |
|
Aha!
Carl
"Val Raemaekers" <val@valtronics.co.za> wrote in message
news:akqvoq$87m$1@news.codecharge.com...
> Hi Carl,
> I am well aware about the documentation that is shipped with coldfusion
> itself.
> The documentation I am after is a codecharge programming reference for
> coldfusion as is provided in the helpfiles that ship with codecharge for
asp
> and php ...
> Val
|
|
|
|
|
