Share a "group" of queries,forms, macros etc. with another user

Ingeneeus

Registered User.
Local time
Today, 07:18
Joined
Jul 29, 2011
Messages
89
I hope this doesn't sound too strange.
I've created a number of interrelated Forms, Queries, Macros, and Reports that are more or less tied to one customer. Since I'm not the only one in our office who works on this account, I'd like to be able to share these tools with the other two people in the office that also work with this customer. This way, I won't be the only one able to perform the functions that this group of Forms, Queries, etc. do.

I've used the "right-click => Add to Group" feature in Access 2003 to create a group that contains all of the needed functions. So far, so good.

This is where I bog down. I'd like to export all of these goodies so that the coworkers in question can add them to their DB, and I'd like to do it all at once instead of individually (there are quite a few items). The thing is that, if I "right-click" on the group folder, I don't seem to have the option to export anything. I have to select one of the items in the group to get the "export" option. Also, all of the items in the "group" folder look like shortcuts, not actual Forms, Queries, etc.

I'm clearly missing something here -- I just don't know what.

Any enlightenment will, as always, be appreciated.
 

Attachments

  • Access Group.jpg
    Access Group.jpg
    56.1 KB · Views: 108
Sadly, export only exports a single object at a time. Create a new empty database and import all the objects into it. You won't get a "Group" view so you'll have to pick them out one at a time but at least it will be easy for your coworkers to import the objects.

I also question why you each have a custom FE. Wouldn't it be better to have a master FE that you all copy for your use. That way you could update the master with tested changes and everyone would copy down a new version.
 
Thanks for your reply, Pat. I was hoping the answer wouldn't be something like that, but am not surprised.

I'm afraid I don't recognize the term "FE." I'm guessing that means the collection of Queries, Forms, Reports that comprise our Access database?

We didn't build the system (as you might guess by my limited knowledge :) ) -- it's a prepackaged order/inventory management, so to use an increasing overused phrase, it is what it is. All of the common data -- Customer Info, Order Details, Inventory, etc. -- resides on our server. All of the, uh, tools, for lack of a better word, reside on our individual workstations. I'm sure there's a reason is was constructed this way -- I just don't know what it is.

The application does have a tool for sharing "custom" Reports and Queries, etc., but it will only do one at a time; I was hoping that there was a more efficient way to get it done. I think your suggestion about creating a kind of temporary db to move the export/import through will certainly help.

Thanks again!
 
FE = front end = forms/reports/queries/macros/code/linked tables
BE = tables

In your case FE would equate to a set of common tools that you all share. It will help with standardization and distribution. I don't think you want different versions of the same forms/reports/queries for each user. Do you?
 
From your description, it sounds like the front end and back end were split, which is generally the ideal scenario once your database is ready for distribution. These are some reasons why it's a good idea to split your application:
1) The BE data needs to be shared by everyone, so it needs to be one file in a centralized area. But, the FE shouldn't be shared as locking issues may occur when sharing the same FE. Complex code execution that take place in the FE may also be noticeably slower when run from the network.
2) When you need to update the design of your application, having the FE and BE split means you can just update the FE without affecting the BE. If you didn't split them, you would end up replacing all your data.
3) You want to give each user their own custom front end, which is a lot simpler to do than to create one front end with user access.

I think what you want might be possible with vbscripts, but I don't know of any. I have seen some vbscript that will write each form, report, macro, etc. into individual text files as well as allow you to put them back together again. Perhaps it could be modified to suit your purposes.
http://stackoverflow.com/questions/187506/how-do-you-use-version-control-with-access-development

Unfortunately, I won't be able to offer much help with this.
 

Users who are viewing this thread

Back
Top Bottom