Any idea why I can no longer select the the reference "Microsoft ADO Ext. 2.8
for DDL and Security?"

It's not in the list anymore?

On Mon, 25 Aug 2008 07:44:02 -0700, JK <jasonk at necoffeeco dot com> wrote:

>Any idea why I can no longer select the the reference "Microsoft ADO Ext. 2.8
>for DDL and Security?"
>
>It's not in the list anymore?

What version of Access?

I know that Access 2007 removed the ability to create Workgroup Security (it
will still use it in .mdb databases if it was created with an earlier
version). Perhaps ADOX has been removed as well.
--

John W. Vinson [MVP]

John W. Vinson <jvinson@STOP_SPAM.WysardOfInfo.com> wrote in
news:v9n5b49s6dpps8b25osvuub4u1sts26d7o@4ax.com:

> On Mon, 25 Aug 2008 07:44:02 -0700, JK <jasonk at necoffeeco dot
> com> wrote:
>
>>Any idea why I can no longer select the the reference "Microsoft
>>ADO Ext. 2.8 for DDL and Security?"
>>
>>It's not in the list anymore?
>
> What version of Access?
>
> I know that Access 2007 removed the ability to create Workgroup
> Security (it will still use it in .mdb databases if it was created
> with an earlier version). Perhaps ADOX has been removed as well.

Why would one ever use any of ADO's ugly stepchildren for
Jet-specific functionality?

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

Yes, it's because you have put the database onto a Windows-Vista machine.
It likes to remove it from databases, but it never comes back if you use it
back on a Windows-XP machine.

I used ADOX to automatically relink my BackEnd database back to a server
when it's in a Business Network, and then switch it back to my BackEnd test
data when I'm developing. It's obvious that many people do their linking
manually considering how many people do not understand what ADOX does.

The best solution I have so far is this:

Sub TestADOX()
On Error Resume Next
If Application.References("ADOX").IsBroken Then
If FileExists("c:\windows\system32\msadox.dll") Then
Application.References.AddFromFile
"c:\windows\system32\msadox.dll"
Else
Application.References.AddFromFile "c:\program files\common
files\system\ado\msadox.dll"
End If
MsgBox "ADOX Error discovered, probably due to being used in
Windows-Vista." _
& " This database needs to restart." _
& vbCrLf & "Press OK to close this application and then restart
again." _
& vbCrLf & "Please contact the database developer if this error
continues."
DoCmd.Quit
End If
End Sub

The bug is has is that it has to close the database before the problem is
fixed.


I hope this is helpful.


Dominic


"JK" <jasonk at necoffeeco dot com> wrote in message
news:F6708620-93D3-4911-998E-D6FB361C8AA8@microsoft.com...
> Any idea why I can no longer select the the reference "Microsoft ADO Ext.
> 2.8
> for DDL and Security?"
>
> It's not in the list anymore?

Ooops, nearly forgot

Function FileExists(strFile As String) As Boolean
On Error Resume Next
Dim intLength As Integer
intLength = Len(Dir(strFile))
FileExists = (Not Err And intLength > 0)
End Function


Dom

"Dominic Vella" <dominic.vella@optusnet.com.au> wrote in message
news:5B603FCE-4066-4E0C-A643-D518414ECDD1@microsoft.com...
> Yes, it's because you have put the database onto a Windows-Vista machine.
> It likes to remove it from databases, but it never comes back if you use
> it back on a Windows-XP machine.
>
> I used ADOX to automatically relink my BackEnd database back to a server
> when it's in a Business Network, and then switch it back to my BackEnd
> test data when I'm developing. It's obvious that many people do their
> linking manually considering how many people do not understand what ADOX
> does.
>
> The best solution I have so far is this:
>
> Sub TestADOX()
> On Error Resume Next
> If Application.References("ADOX").IsBroken Then
> If FileExists("c:\windows\system32\msadox.dll") Then
> Application.References.AddFromFile
> "c:\windows\system32\msadox.dll"
> Else
> Application.References.AddFromFile "c:\program files\common
> files\system\ado\msadox.dll"
> End If
> MsgBox "ADOX Error discovered, probably due to being used in
> Windows-Vista." _
> & " This database needs to restart." _
> & vbCrLf & "Press OK to close this application and then restart
> again." _
> & vbCrLf & "Please contact the database developer if this error
> continues."
> DoCmd.Quit
> End If
> End Sub
>
> The bug is has is that it has to close the database before the problem is
> fixed.
>
>
> I hope this is helpful.
>
>
> Dominic
>
>
> "JK" <jasonk at necoffeeco dot com> wrote in message
> news:F6708620-93D3-4911-998E-D6FB361C8AA8@microsoft.com...
>> Any idea why I can no longer select the the reference "Microsoft ADO Ext.
>> 2.8
>> for DDL and Security?"
>>
>> It's not in the list anymore?
>

"David W. Fenton" <XXXusenet@dfenton.com.invalid> wrote:

>Why would one ever use any of ADO's ugly stepchildren for
>Jet-specific functionality?

Only one reason that I know of.

Fixing AutoNumbers when Access assigns negatives or duplicates
http://www.allenbrowne.com/ser-40.html

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

"Dominic Vella" <dominic.vella@optusnet.com.au> wrote:

> On Error Resume Next

I'd remove the above line and ignore or msgbox the various errors as
appropriate.

> If Application.References("ADOX").IsBroken Then
> If FileExists("c:\windows\system32\msadox.dll") Then
> Application.References.AddFromFile
>"c:\windows\system32\msadox.dll"
> Else
> Application.References.AddFromFile "c:\program files\common
>files\system\ado\msadox.dll"
> End If

This assumes the location of those DLLs which almost all the time will
be correct. But what about those few times when they're elsewhere?

Also you can't add references in an MDE.

> MsgBox "ADOX Error discovered, probably due to being used in
>Windows-Vista." _
> & " This database needs to restart." _

But what if the above lines of code don't work because of another
problem of some sort?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

Yes Tony, I appreciate all of your comments, but it is the best solution I
have got at the moment. Once upon a time linking databases was simple
enough for any of my non-tech customers, but now that MS-Vista unashamedly
corrupts the ADOX reference, has caused no end of trouble to my business
reputation. Other Vista issues (like date picker on date/time fields) have
caused grief, nearly put me out of business.

And you can't say ADOX is not important, otherwise why was it invented in
the first place if it had no purpose. A small list where ADOX has
advantages over ADO in Office2000:
* Creates new databases
* Supports Decimal data types
* Supports Compression attributes for field data
* Creates and edit saved queries that are accessible only through code
(yes there is more, but I think point is made)

Mind you, it was my fault converting to Vista for my development work when
my customers were still on XP.

Fortunately, my clients are starting to convert fully to Vista, fortunately
now being aware of such issues means I have confident answers.

I would welcome any help on restoring ADOX links when returning to WinXP
environments. I would seriously welcome if someone could provide a better
solution than the code I provided.


Dominic

"Tony Toews [MVP]" <ttoews@telusplanet.net> wrote in message
news:uvv6b4po9bd9t0d12dmscq4fovcs128ogh@4ax.com...
> "Dominic Vella" <dominic.vella@optusnet.com.au> wrote:
>
>> On Error Resume Next
>
> I'd remove the above line and ignore or msgbox the various errors as
> appropriate.
>
>> If Application.References("ADOX").IsBroken Then
>> If FileExists("c:\windows\system32\msadox.dll") Then
>> Application.References.AddFromFile
>>"c:\windows\system32\msadox.dll"
>> Else
>> Application.References.AddFromFile "c:\program files\common
>>files\system\ado\msadox.dll"
>> End If
>
> This assumes the location of those DLLs which almost all the time will
> be correct. But what about those few times when they're elsewhere?
>
> Also you can't add references in an MDE.
>
>> MsgBox "ADOX Error discovered, probably due to being used in
>>Windows-Vista." _
>> & " This database needs to restart." _
>
> But what if the above lines of code don't work because of another
> problem of some sort?
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> Microsoft Access Links, Hints, Tips & Accounting Systems at
> http://www.granite.ab.ca/accsmstr.htm
> Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

"Dominic Vella" <dominic.vella@optusnet.com.au> wrote in message
news:OiQbQK1BJHA.1628@TK2MSFTNGP03.phx.gbl...
<snip>
> I would welcome any help on restoring ADOX links when returning to WinXP
> environments. I would seriously welcome if someone could provide a better
> solution than the code I provided.

I haven't personally used it, Dominic, but you might be interested in what
Michael Kaplan says about programmatically fixing references at the
following URL ...

http://www.trigeminal.com/usenet/usenet026.asp?1033

--
Brendan Reynolds

Yes, that's a great read. I particularly think this is heading in the right
direction:
Declare Function DllRegisterServer Lib "<yourlib.dll>" () As Long
It'll take some time before I work out how to make that work for
"msadox.dll". It would be great to find a course that teaches more about
this stuff.

Thanks Brendan

Dominic

"Brendan Reynolds" <brenreyn@discussions.microsoft.com> wrote in message
news:uUbIBz1BJHA.4916@TK2MSFTNGP03.phx.gbl...
> "Dominic Vella" <dominic.vella@optusnet.com.au> wrote in message
> news:OiQbQK1BJHA.1628@TK2MSFTNGP03.phx.gbl...
> <snip>
>> I would welcome any help on restoring ADOX links when returning to WinXP
>> environments. I would seriously welcome if someone could provide a
>> better solution than the code I provided.
>
> I haven't personally used it, Dominic, but you might be interested in what
> Michael Kaplan says about programmatically fixing references at the
> following URL ...
>
> http://www.trigeminal.com/usenet/usenet026.asp?1033
>
> --
> Brendan Reynolds