Converting to accde files

Posted on 2010-08-23
Medium Priority
Last Modified: 2013-12-25
Greetings all ...

A solution I've just received on a different question is (finally!) providing strong encouragement for me to convert my applications to accde/accdb pairs of files. I'm concerned that coding practices I've adopted in the past won't easily support a conversion to an accde environment. At least not without some serious rethinking and quite a bit of recomposition.

To date the structure I've utilized is basic textbook. Two files, one front end and one back end, both mdb or accdb files. Back end file is all tables, front end file is everything else (including an autoexecute macro), with links to all the tables in the back end. Basic beginner textbook.

The most obvious potential conflict I'm envisioning, as I try to convert at least one of these files to a compiled format, is that I have dozens of instances throughout the front end of my apps where queries, based on conditions available at the moment, are created on the fly, executed, and then deleted. Am I right in assuming that those, at least as they're currently structured, won't run in an accde environment?

Let's assume that my rewriting all instances of this 'create/manipulate/delete' coding methodology isn't an option. Is it possible for me, from within the accde file, to direct that these temporary objects be managed on a workspace within another, linked, read/writable accdb file?

I hope I've articulated this little issue clearly. The implications of your responses, regarding the larger general question of 'how to manage multiple linked files', will clearly have a huge bearing on how I view and map out future projects.

I am so grateful for your willingness to lend your expertise to lost souls like me!


Question by:jofoco4
  • 2
  • 2
LVL 86

Accepted Solution

Scott McDaniel (Microsoft Access MVP - EE MVE ) earned 2000 total points
ID: 33501442
You cannot create forms or reports in the .accde environment, but you can create/delete queries, if that's what you're asking.

That said, I've rarely found a need to create/delete querie on the fly. You can always just build a temporary query and work with the QueryDef object as needed.

Author Comment

ID: 33501754
Thanks for this. My apps don't currently create forms or reports, so I think I'm safe on that front.

One quick followup. I don't understand the distinction you draw between "creating/deleting queries on the fly", and "just build a temporary query and work with the QueryDef object as needed".

This confusion is probably my fault, in how I phrased my first question. Building a temporary query and working with the querydef is how I "create/delete queries on the fly". It's likely your response was just confirming for me that this method is generally accepted.

Thanks again for your prompt reply!


LVL 86
ID: 33506098
By "on the fly", I mean actually creating a QueryDef and populating it.

My description was probably not as clear as it should be. I think you're better off creating and storing a query in the database and then just manipulating that query as needed - i.e. change the SQL property to reflect what you need, then "run" that query. Better yet, just use SQL where possible and be done with it!

Author Comment

ID: 33506424
Good thoughts. Thanks.

Featured Post

Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

I have had my own IT business for a very long time. I started mostly with hardware and after about a year started to notice a common theme. I had shelves with software boxes -- Peachtree, Quicken, Sage, Ouickbooks -- and yet most of my clients were…
Code that checks the QuickBooks schema table for non-updateable fields and then disables those controls on a form so users don't try to update them.
In Microsoft Access, when working with VBA, learn some techniques for writing readable and easily maintained code.
Visualize your data even better in Access queries. Given a date and a value, this lesson shows how to compare that value with the previous value, calculate the difference, and display a circle if the value is the same, an up triangle if it increased…

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question