I don't think you can circuvent the security warnings. They are there to warn users about developer activities.
The usual route I know of for this is to use Access or SQL Server 2005 Express as the back end, and a .NET language as the front end. Alternatively, you can use VBScript and make an HTA to run an Access or other back end.
Otherwise you can turn an MDB into an MDE, but it doesn't resolve the Access and warnings issue.
Did that help?
mmcdonal
Look it up at:
http://wrox.books24x7.com