ADP and workgroup files

[mmitchell]

Are workgroup files (.MDW) still used in an Access 2002 project (.ADP ) ?

I am converting an Access 97 .MDB version to to an Access 2002 project (.ADP) and the workgroup administrator is grayed out in the Tools-->Security section when I open my .ADP file.

If it is not, then how do I protect my code (and code from forms) from being seen when using a compiled .ADE?

 

[mmitchell]

One of the main reason is for data access and manipulation speed. From what I have read, it is the faster way to work with the data on SQL Server.

Yes, I don't like giving up local tables!

One thing I don't understand yet, is why, when I create someting or even look at something in code, like a button, I get the login screen?

If there is no workgroup file, how does the new ADP know about my logins?

Might it be because I dragged and dropped some of my forms from the old MDB into the ADP?

 

[SQL_Hell]

You can't. I guess you have pointed out yet another reason to not use .adp's.

There is an option to create an ADE file which is completely secure. ADPs should not be distributed to users.


{Quote] One thing I don't understand yet, is why, when I create someting or even look at something in code, like a button, I get the login screen?

I had this problem, I think it is better to upsize a completely unsecured version of your database, this way Access doesn't get confused.


Pat I have asked this before, but I simply cannot understand your problem with Access project? why is it you are so against this? what problems have you had?

 

[SQL_Hell]

I really don't agree with this Pat, I think saying Microsoft are forcing people to use SQL Server through Access Project is wrong, Access Project is just designed for use with Sql server, for once Microsoft have built in cross compatability.

The reason Access project only works with SQL server is because it incorperates functionality like the Stored procedure designer, you also mention that that most companies that use Access databases do not have professioanl IT people but if their Database has grown beyond the scope of Access then they need to employ a DBA regardless. If they don't employ a DBA and they are only aware of the SQL server route, then surely thats their fault not Microsofts.

I have built and overseen a few Access project front ends and I have only really seen a couple of bugs that are easily sorted out once you know how, but to get a .MDB to work as a front end for SQL server must be lots more hassle to set up, for example how do pass parameters to stored procedures in a mdb?