Re: Force a submit() on parent from child?

The Natural Philosopher said:

Randy Webb wrote:
The Natural Philosopher said the following on 9/15/2007 3:38 AM:
Randy Webb wrote:
The Natural Philosopher said the following on 9/14/2007 6:52 PM:

<snip>

This would be a dummy submit and wouldn't actually update the
database. Although there is no reason why it shouldn't, but if I do
an actual submit/update before calling the sub window, I guess I
lose the code that had decided to do the window spawn...submit being
a sort of 'GOTO' if you like..

Please don't mention GOTO in connection with JS.


Offends your religious beliefs?
;-)

Nah, my common sense.

In principle the sequence of events I want to see, is this:-

User clicks on something.
This spawns a new window, which independently fiddles with the
database.

Instead, you show/hide a div element in the page that has the form in
it that "fiddles with the database".

On closing that window, the main window does a submit(), to force
post data back to the server, and reload it, and the new data.

The part of the form that "fiddles with the database" (Is that
opposed to drumming or guitaring with the database?) is hidden and
shown. When it is filled out, you submit the *entire form* to the
server. The server updates the database and sends a modified page
back to the browser.

Stop making it harder than it has to be.


Randy: hardness is relative. To carry the code for ALL of this would
be a nightmare. Especially as the data sizes grow. Believe me, there
are good reasons to do it this way. I don't want to have to duplicate
code that is already there on a separate screen.

Based on the other recent threads you have posted, I am not convinced of
that. And also because I know better. It is your choice to make it
harder than it has to be, not mine.


Just two points randy.

First, your syntax was all to shit on what you gave me, however the idea
was basically sound. Thank you for that.

Secondly, you cannot possibly know the context of what I am doing here,
and to claim you know what's best for me without that knowledge makes
you a fool or an arrogant prick.

Or far more experienced and competent. Based on your postings,
I know which way I'm leaning.


--

.

Relevant Pages

  • Re: What would you use?
    ... If they want to make use of their existing MS SQL Server then, as Alessandro suggested, you can use SQL Express. ... The database is still full MS SQL Server, so should an office outgrow Express, there's no problem upgrading them. ... It's not the browser interface, it is the difference between Paradox access, especially if on a local network, vs accessing a server database, especially if across the internet. ... a browser app, then there is no reason to *also* maintain a desktop GUI. ...
    (borland.public.delphi.non-technical)
  • Re: Upgrade Access backend to SQL database
    ... end to SQL tables rather than the current Access table structure. ... If the database is well designed in Access and then upgraded to SQL Server ... It's a five-star book at Amazon.com for a very good reason. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Case Senstivity on SQL Server
    ... good reason, but it doesn't sound like there's any reason you need to ... break things if you change the collation of a database. ... The collation of the server instance is set when the instance is ... You can change database collations with ALTER DATABASE, ...
    (microsoft.public.sqlserver.mseq)
  • Re: Detecting number ranges
    ... database 1 is on server 3 ... For that same reason, the input's initially unsorted - it's *mostly* ... jay at jay dot fm | cry or shout or hit. ...
    (comp.lang.ruby)
  • Re: Force a submit() on parent from child?
    ... Although there is no reason why it shouldn't, but if I do an actual submit/update before calling the sub window, I guess I lose the code that had decided to do the window spawn...submit being a sort of 'GOTO' if you like.. ... which independently fiddles with the database. ... you submit the *entire form* to the server. ... Randy: hardness is relative. ...
    (comp.lang.javascript)