Re: Access 97 and Visual Source Safe ( VSS )

> I still have invisible controls on my forms - I use them
> for debugging otherwise unbound fields!

Yes...you make a great point!!! In fact, while I was making
the case that things
can break if you don't use bang..in fact you many
cases do want things to break! (so, my argument goes both ways!!).

As a coding practice, in some cases the reverse practice of placing a
control on the form means that if you remove the control, then code will
break...and that exactly what some want to happen!!

>
> When you work on a secured database in 2003, are all
> the objects given the default security settings for new
> objects? SaveAsText doesn't save the security settings
> of forms.

Yes...the above is the case, and your rightly point out the problem.

I did at least want to point out that you can work on a secured database
with VSS..but you CAN NOT change the security of existing objects.

So, your point about not being able to work on a secured database needs some
clarification., You can work on one..but any changes to security on the
objects can NOT occur while it is under source code control. And, it makes
sense that new objects receive the default..and it also makes sense that you
can not change existing objects security..(since, as you
mention there is NO provisions for this...and yes, you rightly point out the
"saveastext" is how this works. So security settings can NOT be saved via
VSS..and thus they can't be changed (however, existing settings are not
touched).
..
To be clear here, the this means that to modify the security settings, you
need to have everything checked back in..and then remove the application
from
source control (in a2003...if you do a compact and repair...you can remove
it at that point).

So, you *can* work on a secured database, but it is certainly hampered, and
you are MOST fair to point this out....

Hopefully security has been setup before you start working the application
with VSS. And, further, any individual changes to objects in the
application cannot be done while under VSS.

At the end of the day...it think it is quite nice that VSS does work with
a2003. And, the add in provides a UI extension, so that you actually "see" a
check mark, or a lock icon beside each object in the database (I don't know
if previous versions of access had this ability...as I never used VSS with
anything else but a2003).

Here is a few screen shots...and you can see the "check mark" that VSS add
to all objects in access for things I have checked out (and, a lock for
things checked in).

http://www.members.shaw.ca/AlbertKallal/vss/index.htm

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@xxxxxxx
http://www.members.shaw.ca/AlbertKallal




.

Relevant Pages

  • Re: Help to fix error message accessing Help Center
    ... What happens if you reset the Internet Options Security settings back to ... Open the Internet Options in the Control Panel, ... And, yes, the error message was EXACTLY as shown on your web page. ...
    (microsoft.public.windowsxp.help_and_support)
  • ActiveX controls are prohibited
    ... My security settings in IE are the default, ... double checked that the Administrator account is part of the Administrators ... Group, which according to the description, still has complete control over ... in the error page) and did what it said, which is to delete the 2 ActiveX ...
    (microsoft.public.win2000.windows_update)
  • Re: Server cannot access application directory D:xxx. The directory does not exist or is not accessi
    ... different logon session will see it. ... The directory does not exist or is not accessible because of security settings." ... Security settings for directory D:\xxx are the following: Administrator: Full Control ... I have looked up the members of the "Administrators" group: The only member is the "Administrator" User who already had all rights on the directory. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ActiveX controls are prohibited
    ... Ended up being a bad disk block. ... > Group, which according to the description, still has complete control over ... > in the error page) and did what it said, which is to delete the 2 ActiveX ... > install the control, or my security settings ...
    (microsoft.public.win2000.windows_update)