Connect to Oracle using UDL file

Hi,

I find troubles linking MapPoint to my Oracle 8i DataBase. I've created the UDL file. Then, I double-click on it, I set the DataSource attributes and the connection test is OK. I return to MapPoint, I select Data > Link Data, I choose the UDL file created before, a new window ask me for the table to import data from. When I click on the table, an error window tells me something like : "An error has been generated opening : C\mydirectory\mydatasource.udl, MYTABLE". Not very explicit!.

Anybody has any idea?

Thanks a lot in advance.

Miguel.

the correct syntax is LinkData "Filename.udl!TableName"

Unfortunately, using MapPoint application, I don't have the possibility to write the data source in this manner : Filename.udl!TableName. Fisrt, after clicking on Data>DataLink (or CTRL+L) I have to choice the UDL file to connect to the DataBase. The connection with the DataBase works ok because a new window containing all the tables and views appears. Then, I have to choice the Table or View and the connection fails at this moment. The view which I want to link data from is a list of zip codes like the following :

ID ZIP
1 22563
2 12120
3
4 22596

What am I doing wrong?. What are the other alternatives? Would I have to install an Access DataBase and try with? Or would I try writing a VB app ?. Anyway, I would prefer to solve the problem using a UDL over Oracle without VB programming.

Thanks for your help,

Miguel.

Has anyone managed to successfully do this? And how??!!

Using MS MapPoint, (& Streets and Trips,) I found that *sometimes* you have to watch what you import with regard to blank records, or possibly in your case a blank field which is being used for geocoding, ie: zipcode.

While this experience is not specific to .udl file types, you might try a test import range of data (query, view, range, table whatever) that does not have any blanks, at least in any fields that MapPoint looks at (Key, and geocoding fields like: zip, addr1, or any field that is not "Other data" etc.)

If you find that solves the issue, you might edit your tables so that blanks are filled with something else that will not cause an error with MapPoint. If the error still appears, try removing all blanks in fields you assign to "other data" in MapPoint interface as well. Especially if these fields are used for grouping Multi-Symbol Maps, or any action for which MapPoint has to look at them.

Hope this helps,
JSAS