Re: Access DB Issues - Again

My Assumptions:
1. One can use VB.Net Express 2005 to write a client resident
application to
access an .mdb file living on a remote server.
TRUE
2. No Microsoft Access code elements need to reside on the remote
server
except the *.mdb file.
TRUE
3. On the remote server, permissions need be set so that anyone can
have
read access to that Access database.
TRUE to an extent, you could manage the users through the access
database too.
4. The remote server needs to host the .Net Framework 2.0
FALSE each client needs its own framework installed.
Unless its a web application,.
Are all of these assumptions true ?
What am I missing ?

.

Relevant Pages

  • Re: Access DB Issues - Again
    ... Why don't you use whatever wizard to try. ... One can use VB.Net Express 2005 to write a client resident application ... access an .mdb file living on a remote server. ... No Microsoft Access code elements need to reside on the remote server ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Remote Server shell command
    ... which is part of the Windows scripting facilities and ... I have a new Access 2002 client app ... >data stored in a different .mdb file on a remote server. ...
    (microsoft.public.access.modulesdaovba)
  • Remote Server shell command
    ... run a command line program on a remote server? ... I have a new Access 2002 client app ... data stored in a different .mdb file on a remote server. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Access DB Issues - Again
    ... One can use VB.Net Express 2005 to write a client resident application ... access an .mdb file living on a remote server. ... No Microsoft Access code elements need to reside on the remote server ... you can write the connection strings yourself. ...
    (microsoft.public.dotnet.languages.vb)
  • Access DB Issues - Again
    ... Remote server hosts a .mdb file but the client cannot access the DB through ... One can use VB.Net Express 2005 to write a client resident application to ...
    (microsoft.public.dotnet.languages.vb)
Loading