This is a multi-part message in MIME format.
------=_NextPart_000_01AF_01C73B25.375ABA30
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi all,
I am working on a project which will require some data entry for IP =
address (ex: 192.168.1.001). I will like to get some suggestions on how =
to handle this kind of data with some validations. I was thinking in =
having 4 fields to handle each segment and another field to store the =
whole IP, what do you think?
--=20
Edhy Rijo
www.progytech.com
Bronx NY
------=_NextPart_000_01AF_01C73B25.375ABA30
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.5730.11" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi all,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I am working on a project which will =
require some=20
data entry for IP address (ex: 192.168.1.001). I will like to get =
some=20
suggestions on how to handle this kind of data with some =
validations. I=20
was thinking in having 4 fields to handle each segment and another field =
to=20
store the whole IP, what do you think?</FONT></DIV><FONT face=3DArial =
size=3D2>
<DIV><BR>-- <BR>Edhy Rijo<BR><A=20
href=3D"http://www.progytech.com">www.progytech.com</A><BR>Bronx =
NY</DIV>
<DIV> </DIV>
<DIV></FONT> </DIV></BODY></HTML>
------=_NextPart_000_01AF_01C73B25.375ABA30--