Is it possible to use ODBC data source even if MySQL view doesn't contain an unique key?

[mak]

I'm trying to connect to MySQL server via  ODBC.

MySQL views are only open to analyzer such like us.

 

However, it seems most of those views don't contain primary unique key. 

So it keeps showing the error below.

"The selected columns contains some non-unique value.... "

 

Is there any another way to use MySQL data source via ODBC within Filemaker even if the view doesn't contain unique key column?

 

MS Access allows me to do that.

By the way, it's hard for me to add id(serial) to view because I have no permission to it.

 

Any good solution?

[Wim Decorte]

Ask the admins to add a unique serial?

 

FM will try to find a combination of columns that are unique.   That's not as efficient as being able to rely on one known serial column.  It also means that the available columns do not make for unique combinations; which is probably what you are seeing.  So adding columns may increase that likelihood.  But then if you are going to add columns, add the serial

[mak]

Ask the admins to add a unique serial?

 

FM will try to find a combination of columns that are unique.   That's not as efficient as being able to rely on one known serial column.  It also means that the available columns do not make for unique combinations; which is probably what you are seeing.  So adding columns may increase that likelihood.  But then if you are going to add columns, add the serial

Thanks for a reply.

 

What if admins refused to add a unique serial to views?

That's the point.

 

So far, I import all the records to local first so then it doesn't need to have a unique value column.

 

But it's too much work to do summary of all of the records in MySQL server.

 

Any another good way?

[Wim Decorte]

 

 

But it's too much work to do summary of all of the records in MySQL server.

 

 

This I don't follow.  If you import all the data first into a native FM table, then the summary does not happen on MySQL data...

Given that, it comes down to finding an efficient FM way to summarize data.

 

The larger problem is political, not technical: if there is no working relationship with the MySQL admin then that is a HUGE project risk, and I would not want to work with live MySQL data and just do what you do: import all the data into FM and only work with that data.