You'd also have to let them know before registering that an image is needed and how big it can/can't be - many of us don't have an image of ourselves lying around . Also would need a routine to delete images if they cancel/fail the registration.

I'm not trying to be difficult, but the software probably has the process in place that allows the image to be uploaded after registration for a reason.

If you change the process, you have to think out the consequences. Coding the "Happy Path" when everything works as it should is usually pretty easy. Coding for when things don't work as planned is harder. You have to define the specifications for how it can fail and how to handle different failures.

Well, I guess it isn't easy as I thought. I was thinking to creat a register page something like this... where basic information are required.

http://www.vanitydate.com/register.php - http://www.vanitydate.com/register.php

It's not that hard, but you do need to think about it a little more first. The basic things you need to answer are:

Where must the picture be located:

• Does it have to be uploaded, or can they just provide a link to a picture that's stored on another web server?

Size of the Picture:
I can probably come up with a picture that is 5 Kb or one that is 5 Mb. One that is 64 x 64 pixels or one that is 640 x 640 pixels.

• You need to look at where it will be displayed and what dimensions would look good on that page at a couple of different screen resolutions - say at 1024x768 and 800x600.
• You need to think about the physical space you have for storing the pictures and the bandwidth you'd use to display them and weigh them against the legibility of the photo.

Handling the picture and the application:

• What do you need to do if the application uploads ok and passes validation, but the picture doesn't upload.
• What do you need to do if the picture up loads but the app doesn't or it fails validation?

Bad Pictures:

• Some people will send pictures of Brad Pitt, their pets, or their favorite porn shot. Do you delete the picture and the app, or just the picture and give them a time limit to supply a new one?
• Do you need to approve pictures (and possibly applications) before making them available to the public?
• Will people be able to supply a better pic later? - do you have to approve it?

Deleting Applications/Registrations:

• When a persons info is deleted, the picture should be deleted as well.

Some/Many of these items may be covered by the application you're using. You need to figure out what is and what isn't covered.

There is already a place set for uploaded image

resizing feature also ready included in the software.

Approve of the image is also included in the software.

I'm just wondering how I can have my new members register with an image. I'm not really good with asp, most I can do is modify some little coding her and there.

The example you gave uses javascript to validate the fields. Basically, if your app uses javascript for validation, you'd check the field for being empty and dispaly an alert box.

If your form uses server-side asp for validation however, you have to look at the code of whatever form you use, in the <form tag you'll see an action="somepage.asp" field. somepage.asp is the formhandler where your form is validated and processed.

In somepage.asp, you need to check if the field containing the name of the image is blank - request.form("ImageNameField") = "" -  and if it is, do whatenver error routine is in somepage.asp with whatever error message tou need.