Loop through all forms to set Allow Design Changes Property

[AP]

I personally cannot stand the Allow Design Changes property set to
anything other than design view. Is there a way to loop through all
forms and set this property to design view only? There always seem to
be a few forms that slip past and I figured this would be a good way to
make sure they were all changed.
Thanks

[Steve Jorgensen]

On 15 Jun 2005 07:39:29 -0700, "AP" <ap******@thomp songroup.com> wrote:

I personally cannot stand the Allow Design Changes property set to
anything other than design view. Is there a way to loop through all
forms and set this property to design view only? There always seem to
be a few forms that slip past and I figured this would be a good way to
make sure they were all changed.
Thanks

Yes there is. I don't have any code in front of me to remember the exact
statements required, but in general...

- Create an object variable called objForm of type AccessObject, and use it in
a For Each loop over CurrentProject. AllForms.

- Inside this loop, use objForm.Name to determine the form name, open the form
in design view, use Forms(objForm.N ame) to reference the open form, and set
the property, then close the form using the option to save changes.

Before running this code, make sure no forms are open.

[jv]

if you are using ADP, here's the code that I used:

Public Sub UpdateForms()
On Error Resume Next
Dim obj As AccessObject, dbs As Object
Set dbs = Application.Cur rentProject
'Search for open AccessObject objects in AllForms collection.
For Each obj In dbs.AllForms
DoCmd.OpenForm obj.Name, acDesign
If Forms(obj.Name) .AllowDesignCha nges = True Then
Debug.Print "Updating AllowDesignChan ges for " & obj.Name
Forms(obj.Name) .AllowDesignCha nges = False
End If
DoCmd.Close acForm, obj.Name, acSaveYes
Next obj
End Sub

[Steve Jorgensen]

On 15 Jun 2005 08:45:55 -0700, "jv" <ju***********@ hotmail.com> wrote:

if you are using ADP, here's the code that I used:

Public Sub UpdateForms()
On Error Resume Next
Dim obj As AccessObject, dbs As Object
Set dbs = Application.Cur rentProject
'Search for open AccessObject objects in AllForms collection.
For Each obj In dbs.AllForms
DoCmd.OpenForm obj.Name, acDesign
If Forms(obj.Name) .AllowDesignCha nges = True Then
Debug.Print "Updating AllowDesignChan ges for " & obj.Name
Forms(obj.Name) .AllowDesignCha nges = False
End If
DoCmd.Close acForm, obj.Name, acSaveYes
Next obj
End Sub

That code should work fine in either an ADP or an MDB, FWICS.

[David W. Fenton]

Steve Jorgensen <no****@nospam. nospam> wrote in
news:d6******** *************** *********@4ax.c om:

On 15 Jun 2005 07:39:29 -0700, "AP" <ap******@thomp songroup.com>
wrote:

I personally cannot stand the Allow Design Changes property set to
anything other than design view. Is there a way to loop through
all forms and set this property to design view only? There always
seem to be a few forms that slip past and I figured this would be
a good way to make sure they were all changed.
Thanks
Yes there is. I don't have any code in front of me to remember
the exact statements required, but in general...

- Create an object variable called objForm of type AccessObject,
and use it in a For Each loop over CurrentProject. AllForms.

If you're in A97, which didn't have that collection:

CurrentDB.Conta iners("Forms"). Documents
- Inside this loop, use objForm.Name to determine the form name,
open the form in design view, use Forms(objForm.N ame) to reference
the open form, and set the property, then close the form using the
option to save changes.

Before running this code, make sure no forms are open.

Here's the A97 code:

Public Sub turnOffFormProp s()
Dim strForm As String, db As DAO.Database
Dim doc As DAO.Document
Set db = CurrentDb

For Each doc In db.Containers(" Forms").Documen ts
strForm = doc.Name
DoCmd.OpenForm strForm, acDesign
Debug.Print Forms(strForm). Properties("All owDesignChanges ")
Forms(strForm). Properties("All owDesignChanges ") = False
DoCmd.Close acForm, strForm, acSaveYes
Next doc

Set doc = Nothing
db.Close
Set db = Nothing
End Sub

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[David W. Fenton]

Steve Jorgensen <no****@nospam. nospam> wrote in
news:d6******** *************** *********@4ax.c om:

On 15 Jun 2005 07:39:29 -0700, "AP" <ap******@thomp songroup.com>
wrote:

I personally cannot stand the Allow Design Changes property set to
anything other than design view. Is there a way to loop through
all forms and set this property to design view only? There always
seem to be a few forms that slip past and I figured this would be
a good way to make sure they were all changed.
Thanks

Yes there is. I don't have any code in front of me to remember
the exact statements required, but in general...

- Create an object variable called objForm of type AccessObject,
and use it in a For Each loop over CurrentProject. AllForms.

- Inside this loop, use objForm.Name to determine the form name,
open the form in design view, use Forms(objForm.N ame) to reference
the open form, and set the property, then close the form using the
option to save changes.

Before running this code, make sure no forms are open.

Silly me. You don't need to run the code in A97.

DBs converted from A97 either don't have the property or set it to
False, which is one reason why it was ages before I ever even knew
this "feature" existed (and, yes, I mean to ridicule the
introduction of what looks to me like a completely useless feature).

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Arno R]

"David W. Fenton" <dX********@bwa y.net.invalid> schreef in bericht news:Xn******** *************** ***********@24. 168.128.74...

Silly me. You don't need to run the code in A97.

David, did you have your brains dilated today? ;-)

Seriously, I have not noticed the property until this very moment ...
Anyone using it? When?

So we might need:
'GetRidOfAutoCo rrect' (you provided code with this name IIRC)
'GetRidOfSubDat aSheets'
'GetRidOfSomePr ops'

Arno R

[David W. Fenton]

"Arno R" <ar***********@ tiscali.nl> wrote in
news:42******** *************@d reader2.news.ti scali.nl:

"David W. Fenton" <dX********@bwa y.net.invalid> schreef in bericht
news:Xn******** *************** ***********@24. 168.128.74...

Silly me. You don't need to run the code in A97.

David, did you have your brains dilated today? ;-)

Seriously, I have not noticed the property until this very moment
... Anyone using it? When?

So we might need:
'GetRidOfAutoCo rrect' (you provided code with this name
IIRC)
'GetRidOfSubDat aSheets'
'GetRidOfSomePr ops'

Well, I've got code for the first two, plus what I just posted to
get rid of the stupid property that causes property sheets to end up
displayed when you forget to close the property sheet during
development.

That seems like the kind of thing that is going to trip up the
novice more often than the professional, but it's something that
would help only the pro if it had any use at all, so it just seems
like a very dumb feature.

The on thing I *really* wish I could turn off is displaying the
subforms in place! What a colossally stupid feature!

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Arno R]

> The on thing I *really* wish I could turn off is displaying the

subforms in place! What a colossally stupid feature!

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

Michka has a 'solution' (well, it helps...) for that, you know the "TSI Subforminator" I guess?

Also what I do sometimes is:
- Open the subform(s) in design view first, before opening the main form.

Arno R

[David W. Fenton]

"Arno R" <ar***********@ tiscali.nl> wrote in
news:42******** *************@d reader2.news.ti scali.nl:

The on thing I *really* wish I could turn off is displaying the
subforms in place! What a colossally stupid feature!

--
David W. Fenton
http://www.bway.net/~dfenton dfenton at bway dot net
http://www.bway.net/~dfassoc
Michka has a 'solution' (well, it helps...) for that, you know the
"TSI Subforminator" I guess?

I haven't done enough A2K development to download it, but, yes, I
did know about it.
Also what I do sometimes is:
- Open the subform(s) in design view first, before opening the
main form.

That's how I always work.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc