Access Form on Front End and SQL Server on BACK END

I've not learned VB.NET yet. I'm moving from VB6.0. Soo.... I need a quick
way to create a form that will allow me to provide a quick way to input info
into an SQL Server DB until i get up to speed. I've learned that I can using
an Access form on the front end and use SQL Server on the back end.

Here are a few of my concerns.

- From what i undersand, Access is very resource intensive; however, only a
few people will be actually using it.

- I'm using SQL Server because there are several different centers and at
least one person at each center will need to be able to access the DB, sooo...

- Will Access need to be installed on the server? Or will their local
computers,
which already have Access installed on them, be enough?

- Will several users be able to input information into the SQL Server
using the
Access form simultaneously if needed?


Thanks guys!

jacob wrote:
> I've not learned VB.NET yet. I'm moving from VB6.0. Soo.... I need a
> quick way to create a form that will allow me to provide a quick way
> to input info into an SQL Server DB until i get up to speed. I've
> learned that I can using an Access form on the front end and use SQL
> Server on the back end.
>
> Here are a few of my concerns.
>
> - From what i undersand, Access is very resource intensive; however,
> only a few people will be actually using it.

Any front end will be resource intensive if used incorrectly and not
resource intensive if used properly. Access is no better or worse in this
regard.

> - I'm using SQL Server because there are several different centers
> and at least one person at each center will need to be able to access
> the DB, sooo...
>
> - Will Access need to be installed on the server? Or will their
> local computers,
> which already have Access installed on them, be enough?

Installing Access on the server is unnecessary and would accomplish nothing
if you did it.

> - Will several users be able to input information into the SQL
> Server using the
> Access form simultaneously if needed?

Yep. The only problem should be if users try to edit the same *record*
simultaneously. In that case whoever saves first "wins".


--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Thanks very much! There won't be any edits just inserts!