Access based database, how to use the data

[MikesMovies]

Hi all

I've used MS Access a fair bit in the past but am somewhat lost since moving to 2013Pro.

Some years back I was using software to document radio intercepts, this was based on Access but used a program to display and enter the data.
That program was lost after upgrading to a new computer (tied to the CPU)
And the company has long since gone out of business.
So I am left with the MS Access elements.
In the form of a 3mb database that has nothing but a long list of tables to show for itself.
Each table opens and has some ID columns with text like this in them 'L096e0dd24757c1533a7cc153e6ba44bd' and after has usable data.

What I want to do is set up Access so I can use as much of the data as possible.

Cany anyone help me sort this out please?


Kind regards


Mike

 

[jdraw]

Do you have anything in the relationships window (Database Tools->Relationships)?? It might give some info re database structure.

 

[MikesMovies]

Do you have anything in the relationships window (Database Tools->Relationships)?? It might give some info re database structure.

Hi and thanks for getting back to me.

When I click on that I get a little box with all the tables listed and an invite to add?

 

[jdraw]

That's what I was afraid of --- there were no relationships defined, or they were dropped when transferring the database.
Do you understand the "business" (what the tables represent and how the tables are related to each other)?

 

[MikesMovies]

Hi, yes kind of, was a complex data collection tool. At least I can try and extract data out of it and build something myself that is far less complex??? That is what i need help with, how to get the data out and then organise it so i can work with it. Big project I am guessing?

 

[MikesMovies]

Would it help if I sent it to you? zipped up it is just over 600kb.

 

[jdraw]

No, I don't know WHAT the database represents and wouldn't recognize the data.
My suggestion to you is to create a 2-3 line description of each table (and field if necessary).
In order to help you redevelop/develop a smaller version/reengineer what you had, readers need to know:
-what is the database about --overview and progressively more detail
-what does each table represent ( in plain English)
-what are the rules for the Business (needed to relate the tables)
-if we collectively can develop a model of what you have/need, then we/you can work with the data to populate the tables in the model.

You will need some test data and some scenarios re what you will do with the data:
-what reports will you need/do you want
-what form(s) are important for -input, queries, reports, etc
-how many users will there be
-do you have a list of queries/questions you want to "ask" the eventual database?

You are the one who knows:
-what you want
-what you used to have (however, foggy that may be)
-the subject matter

and you will have to transfer/communicate some of that to readers if they are going to offer positive assistance/advice.

The above is my best recommendation.

Post posting comment:

The level of detail you could describe (at least start with) is illustrated in the following scenario:

Pretend you are in a Line up at your favorite fast food facility. Someone you do not know; who does not know you; is not familiar with database nor your issue/opportunity--asks you---- What are you working on these days? What is the issue/opportunity? (We know nothing of you/your issue/your data), so start with that level to get us up to speed.

 

[RainLover]

If you can convert your Database to 2007 we might have a chance to understand what is what.

But you should do as jdraw suggested first.

 

[MikesMovies]

Hi both, many thanks! a fair bit of work all from memory so will take me a while to sort. I'll report back asap. Thanks