Question Compare tabels or columns

[Magnus1982]

Hi,
I am looking way to compare tabels or meby columns.
Let say we have 7 "base" each base have about 120 elements. Some of the elements are the same . I need to create somethink to show which elements are shared and which are unique. Next step will be create query or raport which show sequence for change over to save time. SAMPLE : first 6/5/1/7 etc that will save time. Please help!!!

 

[Uncle Gizmo]

I'm not getting the gist of your question. As an overview I think you need to provide more information, because most of the problems we find with database development is incorrect structure. Getting advice about the structure early on will save you a lot of headaches later on.

 

[HiTechCoach]

Hi,
I am looking way to compare tabels or meby columns.
Let say we have 7 "base" each base have about 120 elements. Some of the elements are the same . I need to create somethink to show which elements are shared and which are unique. Next step will be create query or raport which show sequence for change over to save time. SAMPLE : first 6/5/1/7 etc that will save time. Please help!!!

Are you asking about comparing the database design? Like tabel names, field names, etc?

If yes, have you looked a the built-in database documenter?

Also check oot:

http://www.fmsinc.com/microsoftaccess/bestpractices.html

http://www.accessmvp.com/Strive4Peace/Analyzer.htm

 

[The_Doc_Man]

Here is a simple problem with what you described.

Access can easily work with columns of data pretty much automatically. If you bring in something relating to rows, you are stepping across a single record's fields. For you to compare them, they must be related in some way or they must be of commensurate units. If that is so, your data design is an Excel left-over. Access does not do row-oriented stuff that well except by brute force techniques.

Tell us IN ENGLISH what you are hoping to find or to accomplish. Don't use formulas. But if you wanted to give us a brief overview of your project and this problem, it would be a good thing for us to answer your question.

 

[Magnus1982]

Hi,

On the beginning sorry for my English
Is the production meter .

If you have 7 products and some of them are build using the same elements and we talking about machines and change overs between the product. You are looking way to optimise time ( make shorter) of change over. If you create data base which gonna show you which product you should star produce next ... and replace only some elements you will have the more effective sequence of change over. I am looking proposition how to design my data base.

 

[The_Doc_Man]

Let me try to restate this to see if I got the message...

You have some sort of assembly or tool setup and you make products that have some but not all parts in common. There is a time of refit when you change from one product to another. You want to minimize the time of the refit and hoped that Access might help you determine the optimum.

I have to say I don't have an immediate insight into how to do that kind of optimization. It SEEMS to be some variant of a queueing theory problem (of the "non-equal processor" variety), but it has been years since I dabbled in that particular discipline.

Others here MIGHT have personal experience in this field, but please don't be surprised if you don't get a lot of responses.

Here is the harsh reality of Access. I call these my "Old Programmer's Rules."

1. If you can't do it on paper, you can't do it in Access. Meaning - Access is dumber than a box of rocks. If you don't have a good paper design of your process, a "road map" for lack of a better term, you aren't ready to use Access. You have to know the design of your intended database so well that there is no question as to how to implement it, and that means if you don't know how to work this out on paper then you will not succeed using Access.

2. Access won't tell you anything you didn't tell it first. (or at least tell it HOW to tell you.) - Meaning: It is all about inputs and outputs. You need to know what you need to get out of your application AND what inputs it will take to let Access optimize things for you.

Access is an ORGANIZING tool. You can use the tool to compute anything you know how to compute. And there's the catch. If you don't know how to compute it, NO computer language or tool will make a difference.

Here, then, is the question: Can you write a step-by-step procedure on paper telling you how to determine this answer? Because that is step number one of how to make this happen - and that step is the same for EVERY problem in ANY computer language or tool environment.