OK, do this a little differently

[Chris Chandler]

I want to insert a Excel Web Component into the page. When I click the submit
button the only thing that will submit is the name of the button, what am I
missing here?
I would thik it would be able to submit the content s of the spreadsheet.
Yes I have OWC installed and it works fine, If I could get danged thing to
submit the actual form, it would be great.
Or, could itr be linked to another form locally or something and submit the
data to that form?
Grrr I truly despise doing web work <G>

 

[Jim Buyens]

-----Original Message-----

I want to insert a Excel Web Component into the page.
When I click the submit button the only thing that will
submit is the name of the button, what am I missing here?

This is because Excel Web Component is an ActiveX control.
Therefore, as with any ActiveX control, you have to write
JavaScript that pulls the data you want out of the ActiveX
Control and stuffs it into hidden form fields.

I would thik it would be able to submit the contents of
the spreadsheet.

Yeah, but then what? How would you process that on the
server?

Yes I have OWC installed and it works fine, If I could
get danged thing to submit the actual form, it would be
great.
Or, could itr be linked to another form locally or
something and submit the data to that form?
Grrr I truly despise doing web work <G>

I'm not getting a very good sense of what you're trying to
accomplish. However, there's really no good way to expose
all or part of a spreadsheet so that Web visitors can
update it. Excel is a single-user desktop program, and the
Web is multi-use background.

The best approach is usually to put your data in a
database, and then write HTML forms that update the
database.

And BTW, I really despise programming desktop apps.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Chris Chandler]

The best approach is usually to put your data in a
database, and then write HTML forms that update the
database.

That is actually the conclusion I came to as well. But that is going to be
about 5-8 months down teh road, phase 2 if you will. The company I work for
had absolutely nothing in place or even anything that looked remotely
efficient networking wis. Right now I am putting up online forms so they can
submit their numbers in daily.
The database server is the next plan. It has been a feat to connect 11 stores
across 2 staes when there was absolutely nothing in place. LOL but that was
the easy part, I truly hate doing web design.

 

[Thomas A. Rowe]

All you need is Windows based Web host that support Access and ASP, then the 11 stores would login
to the website to submit their info., then you could download the database, etc.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

 

[Chris Chandler]

All you need is Windows based Web host that support Access and ASP, then
the 11 stores would login to the website to submit their info., then you
could download the database, etc

I thought about that this morning. My intranet server supports ASP. SHould I
set up the DB in Access and put them in a separete location(i.e. Passworded
area) and then set up teh Access page for ach location? Space is not an issue
as far as setting this up this way.
Now I just gotta play with making a DAP

 

[Thomas A. Rowe]

Yes, you would just need a single Access database within a protected area, then you would create the
form(s) in FP. Basically when using Access on the web, it is just a storage container, all
interactivity is handled with ASP/VBScript, not via Access Application interfaces.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================

 

[Jim Buyens]

You're likely to be very disppointed with DAPs. They run as ActiveX
controls within the browser, and need direct file-sharing access to
the database. This is a real show-stopper, except in the most limited
Intranet applications.

Hand-coding your own ASP pages is generally much more successful. For
examples, refer to:

Saving Form Data in a Database
http://www.interlacken.com/winnt/tips/tipshow.aspx?tip=44

Mailing Form Data
http://www.interlacken.com/winnt/tips/tipshow.aspx?tip=46

Of course, using ASP.NET would be even better.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

 

[Chris Chandler]

[email protected] (Jim Buyens) wrote in

You're likely to be very disppointed with DAPs. They run as ActiveX
controls within the browser, and need direct file-sharing access to
the database. This is a real show-stopper, except in the most limited
Intranet applications.

Hand-coding your own ASP pages is generally much more successful. For
examples, refer to:

Saving Form Data in a Database
http://www.interlacken.com/winnt/tips/tipshow.aspx?tip=44

Mailing Form Data
http://www.interlacken.com/winnt/tips/tipshow.aspx?tip=46

Of course, using ASP.NET would be even better.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com

Well I am going to move towards that direction. The go ahead on teh SQL
server is given and I think it will work out better to DB everything. Being
that this is a internal only system it should be too much of a headache
<G>.
NOt sure how a Network guy ended up as an IS Mgr, DBA, Web Admin, etc.,
LOL I am starting to miss SAP.