When I try to create a "Page" web page for data entry, the comb box properties are not transfering to the web page.

As a general rule, the data access pages autogenerated by Access suck sick hairy goat balls. They tend to be buggy, slow, and browser dependent. There are plenty of other ways to do it, but which one you use depends on your server OS and how much control you have over it.

--------------------

quote:

---

Originally posted by Drako:
As a general rule, the data access pages autogenerated by Access suck sick hairy goat balls.

---

I could say the same thing about serverside configuration for Exchange. . .

That being said I have nothing to contribute to this thread. I'm just here for comic relief. Meesa just glad mya voice not high and squeeky like tha Jar Jar Binkses.

--------------------

“I have noticed even people who claim everything is predestined, and that we can do nothing to change it, look before they cross the road.”

“Intelligence is the ability to adapt to change.”

This is the database I created.

My server has mysql installed but I don't know much about mysql. It took me 5 or 6 hours just to figure out basic Access.

I'd like to be able to have the database connected to the website so that:
#1. People who fill out forms on the site have their info go straight to the database so I do not have to manually enter info after I recieve it in the mail. (Which is how I have my forms set up now)

I also need some type of user interface for the database to generate mailing lists and e-mail lists to go to the selected recipiants as well as sort and graph data.

The above access database would be nice to have on the internet because I work from three different locations on 4 different computers. It makes it much more convienient than burning disks everyday or e-mailing info to myself. We also have a cute young office wench who enters data for us and I would like to put in simple protection so she could not accidentally delete the whole thing.

Any takers??? I'm happy to pay for your services. I should do it myself but it means I'll have to go off and buy an SQL book and actually read it and then spend a week screwing up before I get something that works marginally. I would not mind doing this if I were not already working 16 hours a day on other things.

SQL-query :

CREATE TABLE `contacts` (

`Time` VARCHAR NOT NULL ,
`firstname` TEXT NOT NULL ,
`last name` TEXT NOT NULL ,
`address` TEXT NOT NULL ,
`city` TEXT NOT NULL ,
`state` TEXT NOT NULL ,
`zip` TEXT NOT NULL ,
`home phone` TEXT NOT NULL ,
`Cell Phone` TEXT NOT NULL ,
`email address` TEXT NOT NULL ,
`home type` TEXT NOT NULL ,
`price` TEXT NOT NULL ,
`referred by` TEXT NOT NULL ,
`contact date` TEXT NOT NULL ,
`comments` LONGTEXT NOT NULL ,
PRIMARY KEY ( `Time` )
)

MySQL said:

create table contact(
id int not null primary key auto_increment,
name varchar(50) not null,
email varchar(50) not null,
street varchar(50),
city varchar(20),
state varchar(2),
zip varchar(5),
day_phone varchar(12),
cell_phone varchar(12),
home_type int,
price decimal(10,2),
notes text,
reference varchar(50),
created datetime not null
);

I'd suggest you just take the time to learn this stuff for real, or go hire a professional. You're not going to be pleased with your results if you blindly hack your way through this on a need-to-know basis.

--------------------

I've been working with DBs for, like, 15 years. If you have any [more] questions you can post them here or mail them to me. I assume this is related to that little PHP thing we did a few weeks ago?

--------------------

I'm glad to see you're exploring the mysql option because it is FAR superior to using Access. Performing a DSNless connection between PHP and an Access database on a Linux/Apache environment wouldn't have been impossible, but it would have been a huge PITA.

--------------------

--------------------