Makes sense.

Does excel have a way to link two different spreadsheets where changes made
to one will go over to the other? (I don't need instructions on how to do it
yet, I can do more research later, I just need to know IF it can be done)

For example, if I have one spreadsheet listing names, addresses, email
addresses and phone numbers, and another spreadsheet that lists the name
again, the position they play, the high school they attended, their major.
If I delete a record on one spreadsheet, can I set it up to automatically
delete it on the other?

Because the problem I'm having right now in keeping it ALL in Excel is that
there are two many spreadsheets with different info that aren't linked. That
means if one person deletes or adds a player, he may change it on one
spreadsheet but not on the other.

Jo


"CLR" wrote:

Personally, I would stick with Excel. Of course I'm more familiar with it
than I am with Access...(same as your users). Unless you can define a
significant benefit to THEM by switching to Access, they don't need the
aggravation of having to learn new software just to make a change. It just
takes time away from their job.....and in the case of Access, it will take a
lot of time. Technical benefits be dammed.....unless the USER percieves a
benefit, there is none. I once designed an extensive Training Matrix Program
for a Client in Excel..... well over 1000 employees, both active and
inactive. "Someone" convinced them to change the whole thing over to Access
during my absence. The users hated it, too hard for them to
use/learn.....they being Excel people. When I returned, they had me re-do it
again, back in to Excel. And incidently, I did it in Excel '97, because that
was the version most of the users had on their computers. I found that some
of the macros I had written in XL2k would not work in '97 and was having to
constantly make repairs.....so I dropped down to '97 from then on....no more
problems. Some of the users have upgraded to some newer versions of Excel
and the program still works fine. For what it's worth, such has been my
experience.

Vaya con Dios,
Chuck, CABGx3



"Jo4321" wrote:

I kind of crossposted over on the Access forums, but I need some opinions.

I'm in a new job with a college sports team and there is an existing roster
of team members on Excel. It contains all the usual info name, address,
ssn, position played, hght., weight.. etc. There are other spreadsheets with
team member with other info, such as home of record, parents names, summer
address, etc. There are other spreadsheets with
possible recruits with similar information. The coaches are familiar with
the excel format.

I'd like all the info to be in one place. But it seems that if I put it all
into one spreadsheet, it is going to have a heck of a lot of fields and would
be unweldy to view. Plus the possible recruits would be mixed in with the
current team members (even though I'd have a field that could be checked
"team or recruit".

Is there a way to connect the various separate excel spreadsheets somehow so
that they'd work together?
Or is the only way to have these connections by
using a database program such as access?

I use the spreadsheets to generate correspondence, roster lists for the
coaches, labels, nametags, etc. I also use it for reports (names of recruits
who visited etc),The coaches will often use the info by using "save as" and
then deleting the stuff they don't need and adding stuff they do. ( One
example, the "lifting coach" will copy the names and heights and weights and
then add his own columns for their workouts.)

If I switch this stuff over to access, will what I gain in flexiblity be
lost in the coaches ability to manipulate the data themselves? (I could do
the same thing that the lifting coach does by using a directory merge with
word, but the coaches aren't as familiar with mail merge as I am.) There are
many other examples of times when the coaches would need to grab this data,
so I'm wondering if I ought to just leave it all in excel.

So what are the pros/cons access/excel in my situation?

TIA,
Jo