Hi Bonnie,

Thanks for the info. I'm not sure yet if I'll be getting data directly from the GPS either. One of my customers is outfitting his service trucks with GPS units so he can track their location. I want to add lat and long to a service location table for possibly interfacing with MapQuest, MapPoint, or something else.

I'm just in the early stages of this but it's gonna be interesting!

R--

>Hi Roger,
>
>I've dealt with lat/long in the past, but it's been manually input ... I don't know if you'd be getting the data directly from the GPS unit or not (and it may or may not matter), but we've used both char data types (we used char(20), but I think char(10) is sufficient) and numeric(10,6). Do *not* use real datatypes as the precision (or is it scale, I always get it mixed up <g>) is not enough.
>
>~~Bonnie
>
>
>>I'd like the new system I'm building to talk to GPS units (Global Positioning Satellite). I'm pretty sure I'll need to deal with lattitude and longitude but I don't have a clue what data type or column width to use in SQL 2000. Has anyone dealt with this before and could you point me in the right direction?
>>
>>Thanks,
>>Roger