FrontPage 2003 security with Access 2003 Workgroup

[John C.]

Thanks in advance for any help here...

Here is my problem:
I have built a MS Access 2003 database which we are using for a Payroll
System. Currently, our employees submit a timecard (in paper) which I put
into the database every other week. However, the company is expanding and we
are hiring more people. So, I want to try and make it so each employee can
connect to this database and add their biweekly timecard.

Unfortunatly, not everyone has a copy of Access on their computer, so the
Internal Forms in Access aren't a solution. Secondly, we are using the
Access Workgroup for security. For those of us who have Access on our
computer, we have to join a workgroup that has setup Groups with Users and
Passwords.

My goal is to make an interface where each employee could login, with their
own unique user name and password, and have a time card for them to fill out.
So, I tried Data Access Pages (DAP) which are built into Access as a Web
Solution. However, DAPs are HTML pages and thus can not call Access
Funtions, like CurrentUser, which we use in the Database to authenticate the
User and limit his or her access to certain pages.

But, I remembered that FrontPage can connect to a database, and you can
write scripts which automatically fill in certain fields with respect to a
User (aka Name, Employee Number, Department). However, because my Database
is in Workgroup and is secured, FP can't talk to it. When I use the Database
Interface Wizard to connect to the database, the Login.asp fails to do
anything. I believe that the Access Workgroup is preventing FP from
connecting.

I do know that when I return to the default Access Workgroup, then use the
Database Interface Wizard to create a Access Database, it works and there are
no problems with Access taking to FP.

Can anyone help here? How do I get a Workgroup Protected Database to talk
to FP? I can't lose the Workgroup, because it has senstive data and needs a
method of Security for those of us who have Access installed on our computer.
And I know DAP have a method of taking to Access to varify the Access
Workgroup Username/Password. What does it do that FP can't?

Again, thanks for sticking in there and reading this... Any help would be
appreciated!

 

[Stefan B Rusynko]

If the FP site and DB are on the same server try creating a DSN for the DB to allow you to access it from the site


PS
What you are trying to do (the login, and web browser user add/edit of the DB) can not be done w/ the DB wizards and will require
hand coding of ASP of ASP.net server side code
- you can not use Access DAP



| Thanks in advance for any help here...
|
| Here is my problem:
| I have built a MS Access 2003 database which we are using for a Payroll
| System. Currently, our employees submit a timecard (in paper) which I put
| into the database every other week. However, the company is expanding and we
| are hiring more people. So, I want to try and make it so each employee can
| connect to this database and add their biweekly timecard.
|
| Unfortunatly, not everyone has a copy of Access on their computer, so the
| Internal Forms in Access aren't a solution. Secondly, we are using the
| Access Workgroup for security. For those of us who have Access on our
| computer, we have to join a workgroup that has setup Groups with Users and
| Passwords.
|
| My goal is to make an interface where each employee could login, with their
| own unique user name and password, and have a time card for them to fill out.
| So, I tried Data Access Pages (DAP) which are built into Access as a Web
| Solution. However, DAPs are HTML pages and thus can not call Access
| Funtions, like CurrentUser, which we use in the Database to authenticate the
| User and limit his or her access to certain pages.
|
| But, I remembered that FrontPage can connect to a database, and you can
| write scripts which automatically fill in certain fields with respect to a
| User (aka Name, Employee Number, Department). However, because my Database
| is in Workgroup and is secured, FP can't talk to it. When I use the Database
| Interface Wizard to connect to the database, the Login.asp fails to do
| anything. I believe that the Access Workgroup is preventing FP from
| connecting.
|
| I do know that when I return to the default Access Workgroup, then use the
| Database Interface Wizard to create a Access Database, it works and there are
| no problems with Access taking to FP.
|
| Can anyone help here? How do I get a Workgroup Protected Database to talk
| to FP? I can't lose the Workgroup, because it has senstive data and needs a
| method of Security for those of us who have Access installed on our computer.
| And I know DAP have a method of taking to Access to varify the Access
| Workgroup Username/Password. What does it do that FP can't?
|
| Again, thanks for sticking in there and reading this... Any help would be
| appreciated!

 

[John C.]

Thanks Stefan,

This site is run of an internal Windows XP Pro machine, so I setup the DSN.
I chose the System DSN over the File DSN. Is that correct? How do I go
about connecting FP to the DSN?

Secondly, I came to the conclusion that DAP would not work for us. I
understand that I would need to do some coding. I have a copy of the Visual
Studio 2005 Beta 2 that I could use for writing the ASP. Would you recommend
this?

 

[Stefan B Rusynko]

Yes in ODBC Data Sources add your DB (select Microsoft Access Driver) and name it
Then in FP Select Tools Site Settings Database - system data source and it should be there

You can use VS or just hand code
For some sample code see http://www.asp101.com/samples/



| Thanks Stefan,
|
| This site is run of an internal Windows XP Pro machine, so I setup the DSN.
| I chose the System DSN over the File DSN. Is that correct? How do I go
| about connecting FP to the DSN?
|
| Secondly, I came to the conclusion that DAP would not work for us. I
| understand that I would need to do some coding. I have a copy of the Visual
| Studio 2005 Beta 2 that I could use for writing the ASP. Would you recommend
| this?
|
| "Stefan B Rusynko" wrote:
|
| > If the FP site and DB are on the same server try creating a DSN for the DB to allow you to access it from the site
| >
| >
| > PS
| > What you are trying to do (the login, and web browser user add/edit of the DB) can not be done w/ the DB wizards and will
require
| > hand coding of ASP of ASP.net server side code
| > - you can not use Access DAP
| > --
| >
| > _____________________________________________
| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > "Warning - Using the F1 Key will not break anything!" (-;
| > To find the best Newsgroup for FrontPage support see:
| > http://www.net-sites.com/sitebuilder/newsgroups.asp
| > _____________________________________________
| >
| >
| > | Thanks in advance for any help here...
| > |
| > | Here is my problem:
| > | I have built a MS Access 2003 database which we are using for a Payroll
| > | System. Currently, our employees submit a timecard (in paper) which I put
| > | into the database every other week. However, the company is expanding and we
| > | are hiring more people. So, I want to try and make it so each employee can
| > | connect to this database and add their biweekly timecard.
| > |
| > | Unfortunatly, not everyone has a copy of Access on their computer, so the
| > | Internal Forms in Access aren't a solution. Secondly, we are using the
| > | Access Workgroup for security. For those of us who have Access on our
| > | computer, we have to join a workgroup that has setup Groups with Users and
| > | Passwords.
| > |
| > | My goal is to make an interface where each employee could login, with their
| > | own unique user name and password, and have a time card for them to fill out.
| > | So, I tried Data Access Pages (DAP) which are built into Access as a Web
| > | Solution. However, DAPs are HTML pages and thus can not call Access
| > | Funtions, like CurrentUser, which we use in the Database to authenticate the
| > | User and limit his or her access to certain pages.
| > |
| > | But, I remembered that FrontPage can connect to a database, and you can
| > | write scripts which automatically fill in certain fields with respect to a
| > | User (aka Name, Employee Number, Department). However, because my Database
| > | is in Workgroup and is secured, FP can't talk to it. When I use the Database
| > | Interface Wizard to connect to the database, the Login.asp fails to do
| > | anything. I believe that the Access Workgroup is preventing FP from
| > | connecting.
| > |
| > | I do know that when I return to the default Access Workgroup, then use the
| > | Database Interface Wizard to create a Access Database, it works and there are
| > | no problems with Access taking to FP.
| > |
| > | Can anyone help here? How do I get a Workgroup Protected Database to talk
| > | to FP? I can't lose the Workgroup, because it has senstive data and needs a
| > | method of Security for those of us who have Access installed on our computer.
| > | And I know DAP have a method of taking to Access to varify the Access
| > | Workgroup Username/Password. What does it do that FP can't?
| > |
| > | Again, thanks for sticking in there and reading this... Any help would be
| > | appreciated!
| >
| >
| >