I suffer some issues when I refresh the schema during the migration of my
cubes from a dev to a prod server...
the first error during the refresh is:
Cannot create a relation between tables in different DataSets

then if I try to process any dimension or cube I receive this error:
Errors in the high-level relational engine. The following exception occurred
while an operation was being performed on a data source view: Property not
accessible because 'Parent Columns and Child Columns don't have
type-matching columns.'..

and finally if I close and reopen VS2005, I can't open my cube again and
this error appeared:
TITLE: Microsoft Visual Studio
------------------------------

Deserialization failed: Property not accessible because 'Parent Columns and
Child Columns don't have type-matching columns.'.

------------------------------
ADDITIONAL INFORMATION:

Property not accessible because 'Parent Columns and Child Columns don't have
type-matching columns.'. (System.Data)

------------------------------
BUTTONS:

OK
------------------------------

during the refresh there is a lot of changes dteected on relationships
between tables in the database like "FK_X_Y deleted" "FK_X_Y added" (same
name same relation)
but in fact I have only few differences in the schemas
but AS detect a lot of changes in the relationships between the tables (AS
detect that the relation has been removed and recreated!!!)

if I don't refresh the DSV, I can process near everything without any
error!!!!

so... what can I do to refresh my DSV without breaking the entire
metadata????
or how to identify the source of the error in detail? (in the XML file of
the DSV himself...)

thanks.

Jerome.

ok, problem solved...
I remove all the tables involved in the refresh step from the DSV
then I do the refresh
and I add the table again from my database.


"Jeje" <willgart (AT) hotmail (DOT) com> wrote