Don't use Access if you can possibly avoid it. It's not suitable for anything
more than very basic web applications. You will have to do all communication
with the database via OLEDB connections and SQL directly to the Jet engine.
Your database will have to sit on the web server. If for any reason the
database locks up, which can happen easily with an Access DB, your website
will grind to a complete halt.
-Dorian
> Don't use Access if you can possibly avoid it. It's not suitable for anything
> more than very basic web applications. You will have to do all communication
[quoted text clipped - 15 lines]
>
> - Show quoted text -
Well Thank You Very Much, So do you suggest that i learn how to use
another Progam like? ASP 2.0 Net is this easy to learn? as im only an
intermediate Access User as its Stands
mscertified - 11 Jun 2007 23:27 GMT
It depends on what technology your company has and what they use for web
development. Different places use different things. You need to be familiar
with whatever database is to house the data (usually Oracle, SQL Server or
MySQL) plus the method of developing the web pages which could be ASP,
ASP.NET, PHP etc.
> > Don't use Access if you can possibly avoid it. It's not suitable for anything
> > more than very basic web applications. You will have to do all communication
[quoted text clipped - 19 lines]
> another Progam like? ASP 2.0 Net is this easy to learn? as im only an
> intermediate Access User as its Stands