>While I could use 2 servers machines with 2 identical structured databases and then presmably switch connection to use one DSN or the another, I am wandering if there is any other viable solution which would keep both databases on the same server, while application can safely switch between them.
>
>It all depends what you mean by "database". With Oracle you have to be careful in your terminology, coming from SQL Server.
>
>Um, you can have a single Oracle "database" (what SQL Server would call a "server") with many "schemas" (what SQL Server would call a "database") and connect to them from your application by connecting as a different user (because in Oracle "user" and "schema" are almost the same thing).
>
>Does this correspond to your understanding?

Hi Colin,

Well I am still new to Oracle.
You are right, their licencing is not fun at all, wrong terminlogy can get you in trouble <g>

I think I found workable scenario with what they call 'instances'.
So we managed to create two DSNs on two 'instances' which are to two identical *structures* and I can switch between them easily.
Instances internally have identical 'users' , 'schemes' etc and only thing that is diffrent are - actual data.
Both on the same server machine (and 'database' )

Now only thing that can present problem perhaps can be - their representatives <g>
But we are buying per-user licencing, and I will additionaly sweaten them up by talking about OpenSource phenomenon, MySql
and how easy VFP can switch between differen backends... ;)


.