Frontend database question

[TC]

You have posted this as a new thread. No-one has any idea what previous
thread you are referring to! Go back to that thread, hit the Reply button on
your newsreader, & add your question to the top or bottom of the existing
text.

HTH,
TC

 

[ARG]

When you state that each user will have their own copy of
the frontend.. Are you saying that the backend is located
on the network and the frontend should be on each
person's harddrive? Or can I have the frontend on the
server and create a shortcut on each person's desktop?

I would think that if I phyically copied the frontend to
each computer that this would be harder to make changes
than if the frontend was a shortcut on each pc then I
could make the changes and when the users click on the
shortcut they would automaticallly have the latest
version.

Please confirm...

 

[ARG]

This question is not referring to a previous thread by me
but to all of the threads that refer to splitting of a
database to a frontend/backend. I have read many of them
and they all comment on the frontend being on the user's
pc but does not state if the frontend is a shortcut or an
actually copy on each user's harddrive.

I just need clarification on how the users (approximately
20) will be access the frontend database.

Thanks..

 

[Scott McDaniel]

Copy the frontend to each user's workstation, then link the frontend to the
tables.

 

[Kevin3NF]

And to make updating the FE easier, take a look at the AutoFE Updater tool
on Tony Toews' website:

http://www.granite.ab.ca/access/autofe.htm

Free utility I highly recommend.

--
Kevin3NF

Sick of all that junk filling up your mailbox?
http://spamarrest.com/affl?2967001

 

[TC]

Ok, understood.

TC

This question is not referring to a previous thread by me
but to all of the threads that refer to splitting of a
database to a frontend/backend. I have read many of them
and they all comment on the frontend being on the user's
pc but does not state if the frontend is a shortcut or an
actually copy on each user's harddrive.

I just need clarification on how the users (approximately
20) will be access the frontend database.

Thanks..

 

[ARG]

If I copy it to each user's workstation is there an easy
way to update the frontend on each workstation if changes
are made?

Thanks for the clarification

 

[Tim Ferguson]

If I copy it to each user's workstation is there an easy
way to update the frontend on each workstation if changes
are made?

A number of choices:-

- you can provide a shortcut on the users' desktops to a script that will
look for a new version on a server and copy it to the workstation

- you can put the same or similar script in the users' startup scripts

- you can email the users to dowload the new version

- you can do the same using a "message of the day" or a web home page

- you can simply copy the new mdb over their old ones if you have access to
their home drives and their workstations are switched on

In general, the new version will be bug fixes or added functionality, so
the users will be reasonably keen to comply.

B Wishes


Tim F

 

[TC]

(snip)

so the users will be reasonably keen to comply

That would be, the Martian users from outer space?

Users are never keen to comply. That would make life far too easy.

TC

 

[Tim Ferguson]

Users are never keen to comply.

<tee hee>


Tim F