# 3367 Non-Existing Modules Cause Error When Querying Configuration Modules System Table

---

One of my users decided to move his database to a different location (eg from C:\Fred to C:\Bert). My app almost takes account of this, but I had forgotton to allow for the fact that modules now need a path. No problem I though - a quick mod to my moving the database code will sort it out.


Stage 1 - get a list of the modules so I don't have to hard code it

select * from modules

Woops

ElevateDB Error #202 An error occurred with the module StripRTF (The module could not be loaded (OS Error: The specified procedure could not be found.))

Could you change things so that a select on this, and any other similar, table works even if the path is incorrect.