Making a smaller Access Production Database
I am looking at creating a smaller Production use database that only has the valid-to- use parts in it and having a separate Design Database that contains everything including the kitchen sink for creating parts.
Our main Design database as it stands right now contains a lot of imported components from other databases, so many extra parts that it confuses people what parts are valid to use. This is why I want to create a smaller database.
I was also kind of leaning to having the smaller production database copied local to each machine at login since it is a fraction of the size and the performance of having the database local is significantly faster than stored on a server.
Using the Copy Database Entries tool I found it easy to export the folders I wanted, but when setting up that database in E3, I found that it doesn't have the same configuration data of the original database.
Is there a way to copy this data into the smaller database?
I've tested it far enough to see that copied components into the production database will show up in the 'Update All components..." command.
Was this Helpful?
-
If you have a attribute that identifies your "valid" parts, you can create a new a tree structure which would sort your library.
If your dead set on a separate library, experiment with DBTool. You can make a copy of your large "kitchen sink" database and then I THINK it will let you delete just the components and symbols, preserving the configuration data.
Was this Helpful?
0 -
Thanks, Paul.
As a follow on to Paul's comment...
If it's an Access database, you can simply copy and rename. If SQL or Oracle, use DBTool to make a copy. This may require a DBA to create the new blank database prior to using DBTool for the copy. Then use DBUpdate to delete the components and/or symbols you don't want en mass. Reference for deleting is in section 4.4 in the latest DBUpdate documentation.
Was this Helpful?
0
Please sign in to leave a comment.
Comments
2 comments