updating access

[Guest]

I am looking for the best source of data storage and need to have the
information stored in mutliple formats. As of now, it appears that Access is
my best option, however I want to make sure.... So, if I change a field in
one instance in Access, will it change all recurrances?

 

[ChrisM]

I am looking for the best source of data storage and need to have the
information stored in mutliple formats. As of now, it appears that Access
is
my best option, however I want to make sure.... So, if I change a field in
one instance in Access, will it change all recurrances?

What exactly do you mean by 'So, if I change a field in one instance in
Access, will it change all recurrances?'

If you make a change to a field in an Access database then that change will
affect any application that uses that database. It will not change any
fields in any other Access databases though.
Having said that there is somthing called 'Replication' that does somthing
along those lines...

 

[Guest]

What I mean by 'So, if I change a field in one instance in Access, will it
change all recurrances?' requires more explanation than I initially
provided...
I am creating a database which needs to be sorted by two different filters
and exist as two seperate entities as such for accessability. However, the
information will need to be updated and I am wondering if there is any way to
only have to update it in one location and have it automatically update the
other citation of it...

 

[John Vinson]

What I mean by 'So, if I change a field in one instance in Access, will it
change all recurrances?' requires more explanation than I initially
provided...
I am creating a database which needs to be sorted by two different filters
and exist as two seperate entities as such for accessability. However, the
information will need to be updated and I am wondering if there is any way to
only have to update it in one location and have it automatically update the
other citation of it...

You should NOT store the same data redundantly in two places.

As a relational database, you should instead store it ONCE; you can
then display it as many different places (Forms, Reports, queries) as
you wish, all linked to the same table.

Note that Tables *have no order* - they should be viewed as an
unordered "heap" of records. If you want to see the records sorted or
filtered (which are two different operations!!!) you can use Queries
based on the table.

John W. Vinson[MVP]

 

[Guest]

i figured out what i was trying to do....
i did a table with seperate forms to have the information organized in
different manners for accessibility and appropriate usage.