Visual LANSA Forum

Hi everyone,

I have to migrate a customer from IBM I to sqlserver, there are two big procedures with two separate partitions.

I have a problem related to tables:

some tables are defined in both partitions and typically were placed in a common library before LIBONE and LIBTWO or left only in one of the two since both the data and the I/O module were shared

I need to emulate the same situation using sql schemas

I didn't understand how to drive the choice of the schema to use from PartitionOne access LIBTWO


Thanks for the help

Is it possible to use the "OTHER" file concept?

Thanks Cesar I think it could be a solution, but I use them as little as possible. Keep in mind that the definition is already present in both partitions, what I didn't understand how lansa in a database decides which schema to use; probably the solution is to be found in the deployment in the section "Configure the Table Schema Substitution", but I've never used it...

Solved,
just take the dll of partition one, and place it in the execute of partition two