It is dumb to *ever* delete what one does not understand. Please stop now
and limit your experiments to reasonable behavior that does not involve
random deletions.
Thanks,
--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies
This posting is provided "AS IS" with
no warranties, and confers no rights.
"Arno R" <arracomn_o_s_p_a_m@tiscali.nl> wrote in message
news:3fa4e364$0$79338$5fc3050@dreader2.news.tiscal i.nl...[color=blue]
> Huh..., didn't mean to offend anybody ...
> Obviously I 'treated' Access a bit too hard in someone's opinion ?
>
> I am just testing some weird things to find a solution for other issues I[/color]
run into.[color=blue]
>
> Did some more testing:
> I found out that you only need ONE line of code to get the same behaviour.
> This time it is not like "running an acetylene torch" or something like[/color]
that I hope ;-)[color=blue]
>
> Try this on a fresh and new A2k db: CurrentDb.Properties.Delete[/color]
"AccessVersion"[color=blue]
> It is this property that is critical as it seems.
> Of course I can understand that this is a property that is needed...<grin>
>
> Still think it's no good that I can delete this property without any[/color]
warning.[color=blue]
> I had the impression that I couldn't delete some critical build-in[/color]
properties as stated in the help[color=blue]
> (error 3384)
>
> Because I like playing with fire I just did some more testing: ;-)
> Try the same (CurrentDb.Properties.Delete "AccessVersion") in Access97 and[/color]
there is NO problem![color=blue]
> You can even try the loop and still no problem.
>
> Again: As I stated I was just testing ... This is no real-life code of[/color]
course !![color=blue]
>
> Maybe A97 is just more "acetylene torch-resistant?"
>
> Arno R
>
>
> "Michael (michka) Kaplan [MS]" <michkap@online.microsoft.com> schreef in[/color]
bericht[color=blue]
> news:3fa3cd13$1@news.microsoft.com...[color=green]
> > Yes, Lyle is right -- this is NOT a bug, and it is frightening that[/color][/color]
anyone[color=blue][color=green]
> > would think it is.
> >
> > If your db was a abody, this would be like chopping off all of the[/color][/color]
fingers[color=blue][color=green]
> > and toes. What kind of shape would that person be in?
> >
> >
> > --
> > MichKa [MS]
> > NLS Collation/Locale/Keyboard Development
> > Globalization Infrastructure and Font Technologies
> >
> > This posting is provided "AS IS" with
> > no warranties, and confers no rights.
> >
> >
> >
> >
> > "Lyle Fairfield" <MissingAddress@Invalid.Com> wrote in message
> > news:Xns9426642495BA8FFDBA@130.133.1.4...[color=darkred]
> > > "Arno R" <arracomn_o_s_p_a_m@tiscali.nl> wrote in
> > > news:3fa3b948$0$79336$5fc3050@dreader2.news.tiscal i.nl:
> > >
> > > > Hi all
> > > > In another thread I had problems changing db.props
> > > > Another problem I encountered while testing this: db corrupt
> > > > When I deleted db.props through code in a loop I could not start the[/color][/color][/color]
db[color=blue][color=green][color=darkred]
> > > > again ... @#$%$
> > > >
> > > > Warning: Don't just try following code on any existing db. Make sure
> > > > there is a copy! (I did ...)
> > > >
> > > > To test I created a NEW db in A2000 and just set some properties[/color][/color][/color]
(menu[color=blue][color=green][color=darkred]
> > > > StartUpOptions) Props like: AppTitle, StartUpForm,[/color][/color][/color]
StartUpShowDBWindow,[color=blue][color=green][color=darkred]
> > > > StartUpShowStatusBar AllowShortcutMenus, AllowFullMenus,
> > > > AllowBuiltInToolbars, AllowToolbarChanges, AllowSpecialKeys
> > > >
> > > > When you run the following code and close the db, you can't get in
> > > > again. Also compact and repair doesn't work.
> > > >
> > > > (Just tested: Also even without changing or creating any props the[/color][/color][/color]
code[color=blue][color=green][color=darkred]
> > > > kills the db!)
> > > >
> > > > Sub TestProps()
> > > > Dim i As Integer
> > > > On Error Resume Next 'You can't delete build-in props
> > > > For i = 0 To CurrentDb.Properties.Count - 1
> > > > Debug.Print CurrentDb.Properties(i).Name 'just to see what
> > > > happpens CurrentDb.Properties.Delete CurrentDb.Properties(i).Name
> > > > Next i
> > > > End Sub
> > > >
> > > > After running this code and opening the db again:
> > > > Access 'complained' that the db was converted from a previous[/color][/color][/color]
version by[color=blue][color=green][color=darkred]
> > > > using DAO method CompactDatabase etc.
> > > > (Message in Dutch, translation maybe not 100% )
> > > >
> > > > I know I have to treat Access 'gently' but sometimes I really
> > > > #$#%$$^$^%&* Any comments? Anything wrong with the code?
> > > >
> > > > TIA
> > > > Arno R
> > >
> > > I ran an acetylene torch over my hard drive for less than 10 minutes[/color][/color][/color]
and[color=blue][color=green][color=darkred]
> > > my database was corrupted too. Ain't Microsoft BAD!? Huh?
> > >
> > > --
> > > Lyle
> > > (for e-mail refer to
http://ffdba.com/contacts.htm)[/color]
> >
> >[/color]
>
>
>
>
>
>
>[/color]
