I was able to use Neatcd97.mdb for my Office home version under:

http://support.microsoft.com/default...b;en-us;177972

Is there also a 2000 version?

MIKE

I would think the 97 version is still usable. VBA didn't change much (if at
all) between 97 and 2000.

The only major caveat to that might be in whatever DAO routines are
included. "Dim db as Database", "Dim rs as Recordset" should now be more
specific and restated "Dim db as DAO.Database", "Dim rs as DAO.Recordset".
Even that isn't a VB issue, per se, but a references issue because of
conflicts when ADO rather than DAO was crowned as the default data object
reference in 2000.

HTH,
--
George Nicholson

Remove 'Junk' from return address.


"Mike Binger" <(E-Mail Removed)> wrote in message
news:743DC972-1F1B-4F62-BE0F-(E-Mail Removed)...
>I was able to use Neatcd97.mdb for my Office home version under:
>
> http://support.microsoft.com/default...b;en-us;177972
>
> Is there also a 2000 version?
>
> MIKE

I converted it from 97 to 2000. The error I'm getting when I open the
database is:

The expression On Open you entered as the event property setting produced
the following error: Can't find project or library.

The form frmFormTopics doesn't open.

So I'm wondering if a VB reference has to be enabled. Thanks for any help
in advance. MIKE

"George Nicholson" wrote:

> I would think the 97 version is still usable. VBA didn't change much (if at
> all) between 97 and 2000.
>
> The only major caveat to that might be in whatever DAO routines are
> included. "Dim db as Database", "Dim rs as Recordset" should now be more
> specific and restated "Dim db as DAO.Database", "Dim rs as DAO.Recordset".
> Even that isn't a VB issue, per se, but a references issue because of
> conflicts when ADO rather than DAO was crowned as the default data object
> reference in 2000.
>
> HTH,
> --
> George Nicholson
>
> Remove 'Junk' from return address.
>
>
> "Mike Binger" <(E-Mail Removed)> wrote in message
> news:743DC972-1F1B-4F62-BE0F-(E-Mail Removed)...
> >I was able to use Neatcd97.mdb for my Office home version under:
> >
> > http://support.microsoft.com/default...b;en-us;177972
> >
> > Is there also a 2000 version?
> >
> > MIKE
>
>
>

I just enabled DAO 3.6 Object library. Now the error I get is: User-defined
type not defined. MIKE

"George Nicholson" wrote:

> I would think the 97 version is still usable. VBA didn't change much (if at
> all) between 97 and 2000.
>
> The only major caveat to that might be in whatever DAO routines are
> included. "Dim db as Database", "Dim rs as Recordset" should now be more
> specific and restated "Dim db as DAO.Database", "Dim rs as DAO.Recordset".
> Even that isn't a VB issue, per se, but a references issue because of
> conflicts when ADO rather than DAO was crowned as the default data object
> reference in 2000.
>
> HTH,
> --
> George Nicholson
>
> Remove 'Junk' from return address.
>
>
> "Mike Binger" <(E-Mail Removed)> wrote in message
> news:743DC972-1F1B-4F62-BE0F-(E-Mail Removed)...
> >I was able to use Neatcd97.mdb for my Office home version under:
> >
> > http://support.microsoft.com/default...b;en-us;177972
> >
> > Is there also a 2000 version?
> >
> > MIKE
>
>
>

Probably means it's trying to call a function that you don't have a
reference to, and because of that is seeing it as an undimensioned variable.

When you debug that error, what line does it highlight?

--
Message posted via http://www.accessmonster.com

Under the form property On Open, it's an event procedure coded this way:

Private Sub Form_Open(Cancel As Integer)
Me!TopicList.SetFocus
End Sub

When running the form, there is only an OK button, no Debug, and the form
goes back to Design view. MIKE

"Josh Nankivel via AccessMonster.com" wrote:

> Probably means it's trying to call a function that you don't have a
> reference to, and because of that is seeing it as an undimensioned variable.
>
> When you debug that error, what line does it highlight?
>
> --
> Message posted via http://www.accessmonster.com
>