username and password prompt when trying to do SQL queries when connecting Microsoft Access to Delphi 7

calendar_today Asked Apr 23, 2009
thumb_up 11 upvotes
history Updated April 14, 2026

Direct Answer

Simple solution, the LoginPrompt to FALSE on your TAdoDatabase component. Make sure that your query object then is linked to the database component. This is a prose walkthrough, ranked #45th of 67 by community upvote score, from 2009.


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

The scenario as originally posted in 2009

As part of my university coursework, I was asked to design and create an HCI for a shop. Part of it is to connect Delphi 7 to MS Access and run SQL queries. I have the database connected to Delphi, but when I run the program and enter the query it prompts me to enter a username and password to access the database. Does anyone have any ideas on what’s going on? I am stumped for ideas!

Any help is greatly appreciated!

Andy

Why community consensus is tight on this one

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


The Verified Solution — solid answer (above median) (+11)

Verbal answer — walkthrough without a code block

Note: the verified answer is a prose walkthrough. If you need a runnable sample, check Access VBA entries ranked in the top 10 of the same archive.

Simple solution, the LoginPrompt to FALSE on your TAdoDatabase component. Make sure that your query object then is linked to the database component.


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

Ranked #45th in its category — specialized fit

This pattern sits in the 65% 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 2009 and 2026

The answer is 17 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

Is this above-median answer still worth copying?
expand_more

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

The answer has no code block — how do I turn it into a snippet?
expand_more

Use the walkthrough above as a checklist, then open a top-10 Access VBA archive entry for a concrete starting template you can adapt.

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

Published 2009, which is 17 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 #44?
expand_more

The pattern one rank above is “Is the join expression not supported by MS Access?”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 1, Answer-score 11, original post 2009, ranked #45th of 67 in the Access VBA archive. Last regenerated April 14, 2026.

ms-access