Re: Solution Required

Hi Lee,

I noticed you are working on designing a web database project. I work at Databeacon Inc. and I believe our product, Databeacon 5.1, would be a perfect solution to your project. Databeacon is an all java OLAP engine that supports a variety of data sources including ODBC, text files, URL based data sources and standard output from an executable file.

The way it works is; metadata cubes are built using the OLAP engine and stored on a web server. Databeacon will work with any type of web server you may be using. The user connects to the web server using a standard Java enabled web browser and receives a Java applet inside of it. This applet is the Databeacon 'viewer' that allows the user to manipulate the data. The user can create and save a report and even export to a variety of standard formats including MS Word, Excel and PDF files.

 Databeacon's ability to manipulate and nest dimensions will allow you to easily create the specific relations you are looking for. The best part is that the users do not need any software installed to perform any of these operations and it's easy to learn.

 Please visit our website <http://www.databeacon.com> for more information and a free demo version of our product. If you have any questions or inquiries regarding our product, feel free to contact me via email.

Ryan Rebello

Digital Outreach

Databeacon Inc.

rrebello_at_databeacon.com

Get Insight Out at www.databeacon.com

"Lee Osborne" <osbornelee_at_hotmail.com> wrote in message news:989499812.29494.0.nnrp-07.c2de1f0e_at_news.demon.co.uk...
> Hi all,
>
> I'm designing a database model for my first SQL web database project. I
 have
> read as much about this as I can but have no more time to learn more.
>
> Project.
> --------
>
> On-line password protected database. Authorised users can login via a
 login
> screen in the browser. This then gives them a list of menu options that
> allow the user to view certain features/areas.
>
> Requirements.
> --------------
>
> . 5+ levels of user access with several freely assignable features/areas
> available according to the user's assigned access level.
>
> . Users can be searched by various columns which again are freely
 definable
>
> . Users have the usual fields, but have a choice of several company
> division, the choice of access level and a choice of country of residence.
>
>
> Notes.
> -------
>
> . The access levels are freely assignable and can be modified.
>
> . The features/areas can be freely assignable to the relevant access level
> and can be modified.
>
>
>
> I have created the following tables:
>
> userTbl
> accessLevelTbl
> countryTbl
> divisionTbl
> featureTbl
>
> Each table has a ID field as the primary key.
>
> Will this model be ok or are there any problems? What relationships do I
> need to consider?
>
> Any help will be much appreciated,
>
> Thanks
>
> Lee.
>
>
>
Received on Tue May 15 2001 - 21:19:58 CEST