Not sure what I need...

[JeremyH1982]

Hello,

I work for a footwear company, and we have a site, basic design, but I did
up a form on a page, in which a customer can place an order, and since we
don't deal with consumers, and just regular stores, we don't need credit card
information or anything like that, they have accounts with us.

Anyways, we have several style #'s that correlate specifically to style
name's, descriptions, & color. Depending on the style # they type in, depends
on the size run that would be available.

As of right now, it's all manually entered by the customer, I would like it
so when they type in a style #, the rest automatically populates, and a drop
down list is available with the sizes available for that size run.

I'm not sure what I'm looking to do, or rather, i'm not sure what needs to
be done to be able to do what i want done. I do know I need a database, or
something with all the information, not sure if i can do a .csv; if a
database, odbc? that would be the easiest for me to create and import the
data from our company software.

This is probably super simple, I'm just not sure what I'm looking to do, or
the proper terminology for what i want to do.

Any help would be greatly appreciated.

 

[Stefan B Rusynko]

Yes a database and custom server side code to query the database (for the form info) and collect the order info, update the database
is what you need

What type of database and server side code you should use
- depends on what your host supports and what your store system supports as data export

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
_____________________________________________


Hello,

I work for a footwear company, and we have a site, basic design, but I did
up a form on a page, in which a customer can place an order, and since we
don't deal with consumers, and just regular stores, we don't need credit card
information or anything like that, they have accounts with us.

Anyways, we have several style #'s that correlate specifically to style
name's, descriptions, & color. Depending on the style # they type in, depends
on the size run that would be available.

As of right now, it's all manually entered by the customer, I would like it
so when they type in a style #, the rest automatically populates, and a drop
down list is available with the sizes available for that size run.

I'm not sure what I'm looking to do, or rather, i'm not sure what needs to
be done to be able to do what i want done. I do know I need a database, or
something with all the information, not sure if i can do a .csv; if a
database, odbc? that would be the easiest for me to create and import the
data from our company software.

This is probably super simple, I'm just not sure what I'm looking to do, or
the proper terminology for what i want to do.

Any help would be greatly appreciated.

 

[JeremyH1982]

Yes a database and custom server side code to query the database (for the form info) and collect the order info, update the database
is what you need

What type of database and server side code you should use
- depends on what your host supports and what your store system supports as data export

our site is not technically a store. It's original and current purpose is
for informational use. But back in December when we were off for an entire
week, I wanted to give our customers an option to place an order even though
nobody's here. They do have the option to email an order, but figured why not
put a form on the website. I'd give you the address, but I'm a little
embarrassed by it, it seriously needs to be updated, or rather, redone.

We host with Network Solutions, and we are on a Windows Platform, which only
supports MS SQL, Access, & ASP/ASP.NET; I would love to switch to a Unix
Based server, to pick up PHP Capabilities, but I would loose the Frontpage
extensions I need.

Also, when someone "Submits" an order, it gets emailed to me instead of
stored on the server. Just thought that would be pertinent...