Hi Sergey

>It looks like a I'm missing something because I din't see where in your application you will use that unique ID you're trying to create.

You are not missing something, but I am not able to explain my thoughts in words, sorry.

I had wanted to append the unique ID (for eg. 12345 and 67890) to the ODBC u.d.s. So I had planned to change the original ODBC u.s.d. C13_VSO3Data_FB, to something like C13_VSO3Data_FB_12345 for first copy and C13_VSO3Data_FB_67890 for the second copy of the app. But then my RV will stop working as on the development machine I have stored in the RV connection as C13_VSO3Data_FB


>>>I'm not sure why it has to be related to used directory in any way. You can generate GUID, for example, and store it in your application configuration file and use for the registry to.
>>
>>Suppose I could but the RV I have created in the app's dbc uses "Connections" to which I have specified C13_VSO3Data_FB.
>>
>>Plus I also use a third party "Report Manager", well it too relies on ODBC users data sources which also points to C13_VSO3Data_FB as the data source.
>>
>>Now both the copy of the app relies heavily on C13_VSO3Data_FB but both want this ODBC user data source to point to their own data. So not only 2 copies of the app, but there are also 2 copies of data.
>>
>>My app has the code to always regenerate the ODBC user data sources, namely C13_VSO3Data_FB. So the first copy of the app will make it point to it's own data. Now I also start the second copy of the app, now it too changes the ODBC user data source C13_VSO3Data_FB to point now to it's own second copy of data.
>>
>>Question: What data will the first copy of the app use when I switch to it using Alt+Tab (both the copies are running)? The first copy relies on ODBC user data source C13_VSO3Data_FB which, now as the second copy has also been run, this points to the second copy of the data but I am trying to use the data of the first copy itself.
>>
>>Hope I have been able to explain my situation.