> > Oops! Two little hitches in the gitalong here. How do you stop the messages that the Registry wants to force upon you? Like, "Are you sure you want to update this information into the Registry?" and "Information in xyz.reg has been successfully entered into the Registry" messageboxes.
>
> REGEDIT takes a "/s" parameter to run in silent mode. You could try passing that as a parameter in the Shellexecute call. I confess I have never worried about trying to suppress the messages, but if you really must do it silently you could always call RegEdit directly:
>
> RUN regedit /s 'F:\DRIPS\SQL_Scripts\CCSRemote.reg' /n
>

And now we're into REGEDIT? Never occurred to me to look at that command for a way to skin this cat. I certainly need to keep messages like that OFF of my app because this app is for a certain profession that would rather not use an app than risk hurting their customer information. I want no unnecessary red-appearing flags.

Now, in your recent Advisor article on this subject, you mentioned that there is no need to put information about your DSN in the ODBC Data Sources subkey, especially to keep people from breaking your DSN connection, but you still need two things, right? You need the connection defined in ODBC.INI and you need the driver defined in ODBCINST.INI, correct?

Here's the problem that has me bloodying my forehead against my monitor. I am writing a Fox app that needs to talk to and monitor a third-party app that was written in Delphi. They advocate using the DBISAM driver to talk to their database, and the version of DBISAM that I purchased allows for a run-time version to be freely distributed with my app. So far, so good.

So, I drop the DBISAM driver DLL into my distribution directory and set up a ODBC.INI setting pointing to it, but that connection cannot be found in Foxpro. I try manually setting up the connection (in code) but all I get are connectivity errors. I try setting up a connection string and - well, don't get me started on all the "unrecognized phrase or keyword" errors and "no driver found" messages I waded through with that attempt! OBVIOUSLY, I do not understand ODBC/DSN magic.

I suppose I could wade into a FileDSN setting, but then I'm exposing the app to risk as the user can easily mess with that with notepad.

So, I walked into the office this morning planning to do what your article said not to do, to code the registry settings directly. And, it looks like I need to code both the dsn for the connection, and the driver, too. But if I can make this regedit work, that will be all the better because I can build the .reg file with set textmerge using the directories I have in place and my driver.

I will give it a try. Thank you for your perseverance with me on this thread. I can only hope that this helps someone else who has the same issue, for I'm sure I'm not alone on this kind of problem.

RLS

Randy L. Smith
Saphea, Inc.
www.saphea.com