Sounds as though your IT department doesn't know what they're talking about.
If they don't allow office files on the server, how are multiple users going
to access the same file?
If you follow Rick's advice and ensure that each user has his/her own copy
of the front-end database on his/her hard drive (with the shared back-end
database on the server), you should be fine.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)
"thread" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
hi rick
after talking with our IT department they are not accepting office file
on the server but one thing that they say and i want to consule you
regarding this issue is that this front-end file cannot stand a
multiple use of users and after some time it can crush down,what do you
say about this?
Rick Brandt ???:
> "thread" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > hi all,
> > i'm going to poblish my access file after dividing it to 2(db and
> > aplications/quries)
> > i would like to know what is the best solution for using the access on
> > the server and what is the best server of course,i know that there is a
> > server called IIS but does it works with access file or i need to
> > change all the platform of my dababase?
>
> In a standard split-app setup you save the data file on the server and
> give all
> users full permissions to that folder. Then the front end is installed on
> each
> user's PC along with Microsoft Access (licensed or the runtime).
>
> The server is merely serving the file. That's it. Think of it as a
> remote hard
> drive. There is no requirement for any other software to be installed on
> it.
> Your app is not running ON the server. It is running on each user's PC.
>
> --
> Rick Brandt, Microsoft Access MVP
> Email (as appropriate) to...
> RBrandt at Hunter dot com