🚀 go-pugleaf

> :) Yeah.  Didn't realize that you did ADO and would be in the same shoes.

I'm not as versed in ADO as with the rest of the VCL but I know enough to be 
dangerous.

> We lock/freeze when we run the app in debugger, with UAC turned off
> completely or turned on - deson't seem to matter.

If you lock when you run the app then try running BCB6 as administrator. 
This is what I have to do when I debug administrative applications.

> It's an MS SQL app using ADO to connect with it.

To eliminate the UAC and administrative privileges have you tried connecting 
via a plain Jet connection yet?  If even that doesn't work then I'm afraid 
I'd be out of ideas since that's about as general a connection as one can 
create using ADO.  The only step at that point would be to make sure you 
have all of the correct drivers installed.

If the Jet connection succeeds then we can move to the next step?  Have you 
added a Vista manifest resource to your application yet?  If not, here is 
the resource that I use which tells Vista to run the application with 
administrative privileges:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level="requireAdministrator" />
      </requestedPrivileges>
    </security>
  </trustInfo>
</assembly>

If you need a RES file for that let me know and I'll email it (or put in 
.attachments).

>  Provider=SQLOLEDB.1;Integrated Security=SSPI;Data Source=MyServer;
>  Initial Catalog=MyDB;

Do you have a SQLServer database that doesn't require integrated security? 
Try using a standard username and password logon and see if that can get in. 
That's the way we have our SQLServer connections set up here (we haven't 
gotten too fancy with security settings yet).

HTH,
Clayton