access database to work with MapInfo

[Guest]

Can an access database work with MapInfo. I don't have the physical access to
work with MapInfo and it is too expensive to purchase. Has anyone worked with
a database that worked in combination with MapInfo. I have found on the web
that having the X and Y coordinates in separate columns is necessary to
import from Access to MapInfo. I am working on a way to import Waypoints
download from GPS to access database, but difficulty is that users don't set
unique waypoint numbers from one location to another several kilometres away.
Has anyone got some pointers for this situation? Any info would help.

 

[James Hahn]

It's not clear what you are trying to do. Why do you want an Access
database to work with MapInfo when you don't have access to MapInfo? If you
are asking whether data in MapInfo import export format (MID/MIF) can be
converted to an Access database, then the answer is yes, because there are a
number of data converters that can create plain text from MID/MIF files that
can then be massaged into a suitable format for import into Access.

Your problem with creating a database of waypoints lies in the method of
downloading from the GPS device. Ensure that the download file includes the
unique internal waypoint identifier and use that, rather than the user
label, to identify the data points.

 

[Guest]

Thank your for your reply.The tip about the download from the GPS is great.

Re: MapInfo
Looking for a way to collect field data electronically and then load into
MapInfo, thought an access database on a laptop would be easy approach. For
users to use MapInfo is a lot of training and some of them find it too
technical. Being able to locate trees spatially and keep records of hazards
and inspections is important. An access database would give easy usability to
the data, but will not put info on a map. Any thoughts to help with direction
to pursue?

 

[Guest]

Extra info to add to reply:
Cleint's organisation has MapInfo which is used for some departments, was
interested in extending MapInfo to his area of interest, but not sure if
worth the effort.

 

[Guest]

I've used Access in combination with Mapinfo. One way around your problem is
to use the primary key feature in your database plus a date time field. You
then run a Make a Table query but create an expression that concatenates the
Primary Key number with the date time field, (I assume your GPS has a
downloadable date/time feature that attaches itself to the waypoint) with a
defined seperator so that your final object identifier looks like e.g
1/12/11/2004 17:35.(Object1/Day/month/Year[UK style] Time GPS Reading
Taken)This whole field should then be accepted by Mapinfo. You then use the
table you've newly made as your Mapinfo Import Table. If it doesn't because
the latest version of Mapinfo has some strange quirks i.e. It won't open
earlier Workspace creations, then set the newly created field format as text,
that should then work OK. The other thing you need to do is to make sure that
you set the field format properties correctly in Access so that you get day
to day consistency, in order for the SQL Queries in Mapinfo to give you the
right result.
I know the real Mapinfo Specialists will say this is not absolutely
necessary but I've found that if you put the X,Y Co-ordinates in field 1 & 2
or 2 & 3 in your database it's easier to locate any faults if your Mapinfo
Create Points action falls over and your objects don't show on the map.

 

[Guest]

Thanks for your reply. Pleased to know of at least person who has done it
and can get it to work.

Liz James

I've used Access in combination with Mapinfo. One way around your problem is
to use the primary key feature in your database plus a date time field. You
then run a Make a Table query but create an expression that concatenates the
Primary Key number with the date time field, (I assume your GPS has a
downloadable date/time feature that attaches itself to the waypoint) with a
defined seperator so that your final object identifier looks like e.g
1/12/11/2004 17:35.(Object1/Day/month/Year[UK style] Time GPS Reading
Taken)This whole field should then be accepted by Mapinfo. You then use the
table you've newly made as your Mapinfo Import Table. If it doesn't because
the latest version of Mapinfo has some strange quirks i.e. It won't open
earlier Workspace creations, then set the newly created field format as text,
that should then work OK. The other thing you need to do is to make sure that
you set the field format properties correctly in Access so that you get day
to day consistency, in order for the SQL Queries in Mapinfo to give you the
right result.
I know the real Mapinfo Specialists will say this is not absolutely
necessary but I've found that if you put the X,Y Co-ordinates in field 1 & 2
or 2 & 3 in your database it's easier to locate any faults if your Mapinfo
Create Points action falls over and your objects don't show on the map.

..