TOPIC: Access Violation in FireDAC Explorer

When trying to drill down in a database (SQLite) using FireDac Explorer it fails with an Access Violation Error message (Access violation at address 0C27783 in module 'FDExplorer.exe'. Read of address 00000000.)

This happens in all databases with this tool.

FireDAC version (via AppMethod 1.15): 21.0.17017 (Build 3725).

Anyone else with the same problem ? Any workaround ?

(memory address above seems to change between startups of program).

Tested FireDAC Explorer v21.0.17017.3725 (run as Administrator from Windows Explorer) still same error,

Tested FireDAC Explorer v20.0.16277.1276 (provided by AM 1.14), everything seemed to be ok.

Will use the last one until there is an update, checking with "Check for Updates" will not function.

Anyone who knows if FDExplorer can be downloaded elsewhere ?

I'm not sure why you are seeing this unless you installed RAD Studio and Appmethod on the same box possibly. The docs warn against this and there are a few shared resources that don't play nice with each other.

Instead of using the FDExplorer standalone app have you tried the integrated functionality? When looking at the default IDE layout in RAD Studio or Appmethod, you should see the Project Manager in the upper right pane. Click the "Data Explorer" tab and use that just the same as you may with FDExplorer.

No, RAD studio and AM is not installed on the same Box.

But I hav both AM 1.14 and AM 1.15 installed on the same Box.

I get same errormessage if I start FDexplorer from the IDE (AM 1.15) menu or from the browser in the AM 1.15 "bin" directory.
FDExplorer seems to work until you try to drill down into a table of a database.

I tried starting Fdexplorer with "Start as Administrator" if the problem was some sort of access violation related to Administrator settings etc, but that didn't help.

Anyhow, The FDExplorer in the AM 1.14 directory behaves correctly, and this rescues me just now.

...and YES !! The data explorer will help a little !!

Good tip!

Observed the exact same behavior. I have XE5 and XE7 installed. If I use the XE7 version, I get the Access Violation, if refer back to the XE5 instance, it runs fine. Looks like I may have to uninstall and reinstall with just XE7