In the past, ever recompose has caused the loss of a ODBC connection with a small number of Excel users. Now we're implementing DEM. I ran the application profiler for ODBC Data Sources, and it c...
See more...
In the past, ever recompose has caused the loss of a ODBC connection with a small number of Excel users. Now we're implementing DEM. I ran the application profiler for ODBC Data Sources, and it captured the registry keys well enough, but it reported C:\Windows\ODBC.INI was unsupported by the flex config file, as well as PIP\srvsvc and PIPE\wksvc. I did a bit a searching, and I found absolutely no discussion or tips or anything about how to handle these unsupported files. In this particular case, I can see the proper ODBC.INI is already save to the golden image. No a problem. But my company has a few software packages that decided to go against to flow and not save their data in C:\ProgramData or in %User%\AppData, but instead chooses its path to C:\U2. How do I preserve that?
