visualAd
Oct 31st, 2008, 10:57 AM
I have been asked by work to develop a web site which allows the update and viewing of an Access database (unfortunately MSSQL is not an option they are willing to consider so I am stuck with access).
In addition, I have also been asked to publish the site on a sharepoint site on the Intranet. I was shown by another employee how I could drag and drop the database onto Sharepoint and how I could create my own "web page" with some rudimentary HTML code to do things like embolden and italicize text on the page. I am a little concerned that this does not meet the requirements of the task in hand :D
As I have very limited experience with Sharepoint I am unsure exactly what it is capable of. A couple of colleagues have hinted that it can do a lot more provided I am supplied with the appropriate access rights. However, I have a sneeky feeling that the interfacing with Access databases may be somewhat limited if it exists at all.
The most obvious solution to me would be an IIS server with a small ASP.NET front end which talks with the database. But, if sharepoint already has these capabilities then there is no point wasting my time re-inventing the wheel.
Can anyone give me an indication as to weather or not this is a feasible idea and if so; what level of customization one would have?
In addition, I have also been asked to publish the site on a sharepoint site on the Intranet. I was shown by another employee how I could drag and drop the database onto Sharepoint and how I could create my own "web page" with some rudimentary HTML code to do things like embolden and italicize text on the page. I am a little concerned that this does not meet the requirements of the task in hand :D
As I have very limited experience with Sharepoint I am unsure exactly what it is capable of. A couple of colleagues have hinted that it can do a lot more provided I am supplied with the appropriate access rights. However, I have a sneeky feeling that the interfacing with Access databases may be somewhat limited if it exists at all.
The most obvious solution to me would be an IIS server with a small ASP.NET front end which talks with the database. But, if sharepoint already has these capabilities then there is no point wasting my time re-inventing the wheel.
Can anyone give me an indication as to weather or not this is a feasible idea and if so; what level of customization one would have?