If you are running some initial application just once on every users database, then you may be right.  It may be easier and faster to use the Object Mapper.

 

Sorry the problem that I have is, I can't convert 200 users and setup database relationhips every time, It will take to long.

So what I'm asking is will the Object Mapper be powerfull enought so I  can setup these realtions manualy.

 

Then all I have to do is convert the databases then work with 1 buisness model with all the manual relationships that I have setup.

 

You see all 200 users are in different states and each one will be converted to a central databse with there own databases using MSSQL.

 

Will this work ?

 

 

 

 

I would choose Option 1.

 

I would start with a converter tool if you have one that you like.  Then I would add the relations to the database manually rather than use the Object Mapper.  If you do this right, when you open up the Object Mappe for the first time, all your relations should be there.

 

DevForce won't help you with the conversion process.  It will help you in your development once you have finished your conversion.

Hi There

 

 

I was told that with MYSQL the table format needs to be INNODB for relations to work and all my clients is set to MYISAM.

 

No in your point of view - what will be the right way to do this.

 

1: Use a convert tool like "Full convert entrprise" and convert all the tables to MSSQL and do development on seting up manual relationship between tables, leaving the new MSSQL database structure like is.

 

2: Create a all new database using MSSQL with relations,

But then how will I convert all my 200 users then. My users is all remote users with different MYSQL databases witch sits localy on there drives.

 

 

How and what steps must I take to use "Devforce" for this development - I AM WILLING TO BUY THE NEW DEVFORCE EF IF you can give me a solution.