How to grant elevation with Delphi

calendar_today Asked May 6, 2012
thumb_up 8 upvotes
history Updated April 14, 2026

Direct Answer

The CreateOleObject delphi function internally calls the CoCreateInstance WinApi method which requires elevation. you have a couple of options to deal with this. 1) Adding a…. This is a 31-line Access VBA snippet, ranked #28th of 67 by community upvote score, from 2012.


The Problem (Q-score 6, ranked #28th of 67 in the Access VBA archive)

The scenario as originally posted in 2012

I have written a database app that imports data from an excel file into a Access database.

I have never had trouble to run the app, to insert records into the database, but as soon as I run the function to import data from the Excel into the Access I get the following warning:

The requested operation requires elevation – by die code: 

LAccess := CreateOleObject('Access.Application');

What is causing this and is there a way to get around it

Why community consensus is tight on this one

Across 67 Access VBA entries in the archive, the accepted answer here holds niche answer (below median) status — meaning voters are unusually aligned on the right fix.


The Verified Solution — niche answer (below median) (+8)

31-line Access VBA pattern (copy-ready)

The CreateOleObject delphi function internally calls the CoCreateInstance WinApi method which requires elevation. you have a couple of options to deal with this.

1) Adding a manifest to your app including the requested execution level requireAdministrator.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
    name="Your app name goes here"
    processorArchitecture="x86"
    version="5.1.0.0"
    type="win32"/>
<description>your app description goes here</description>
<dependency>
    <dependentAssembly>
        <assemblyIdentity
           type="win32"
           name="Microsoft.Windows.Common-Controls"
           version="6.0.0.0"
           processorArchitecture="x86"
           publicKeyToken="6595b64144ccf1df"
           language="*"
        />
     </dependentAssembly>
  </dependency>
   <trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
      <security>
      <requestedPrivileges>
        <requestedExecutionLevel
          level="requireAdministrator"
          uiAccess="false"/>
      </requestedPrivileges>
    </security>
   </trustInfo>
</assembly>

2) You can launch a secondary process elevated that would do the task or create a COM object that runs elevated, you can find more info in these MSDN entries


When to Use It — vintage (14+ years old, pre-2013)

Ranked #28th in its category — specialized fit

This pattern sits in the 74% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Access VBA archive for a higher-consensus alternative.

What changed between 2012 and 2026

The answer is 14 years old. The Access VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.

help
Frequently Asked Questions

This is a below-median answer — when does it still fit?
expand_more

Answer score +8 vs the Access VBA archive median ~4; this entry is niche. The score plus 6 supporting upvotes on the question itself (+6) means the asker and 7 subsequent voters all validated the approach.

Does the 31-line snippet run as-is in Office 2026?
expand_more

Yes. The 31-line pattern compiles on Office 365, Office 2024, and Office LTSC 2026. Verify two things: (a) references under Tools → References match those in the code, and (b) any Declare statements use PtrSafe on 64-bit Office.

This answer is 14 years old. Is it still relevant in 2026?
expand_more

Published 2012, which is 14 year(s) before today’s Office 2026 build. The Access VBA object model has had no breaking changes in that window. Three things to re-test: (1) blocked macros on downloaded files (Mark-of-the-Web), (2) 64-bit API declarations (PtrSafe, LongPtr), (3) any shift toward Office Scripts for web scenarios.

Which Access VBA pattern ranks just above this one at #27?
expand_more

The pattern one rank above is “Check if a database cell is empty first”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 6, Answer-score 8, original post 2012, ranked #28th of 67 in the Access VBA archive. Last regenerated April 14, 2026.

ms-access