Run Time Error 429

[Guest]

I created an application that I was able to use for several months. Now,
when I start various portions, I get a "Run-Time Error 429 ActiveX cannot do
something" error. I have tried re-installing office, running regsvr,
deleting the DAo folder and re-installing everything all over again. The
application works on other pcs but not mine anymore....

the code is:
Set rs = Me.Recordset.Clone

I tried changing it to
Set rs = dbengine.Me.Recordset.Clone

but that just made another error.

Anyone have any ideas? Please let me know.

 

[Ken Snell [MVP]]

Can you give us more info about the context of this code step...such as
posting more of the code both before and after it?

Have you checked the references in the database to be sure none are missing?

 

[Guest]

Here is the rest of the code for this procedure. It looks for the next
available number in the database when the "Current" event occurs.

Private Sub Form_Current()
Dim rs As Object
Dim NewNumber As Integer
Dim CurrentNumber As Integer

AlreadyAsked = False

Set rs = Me.Recordset.Clone
If JustDeleted Then
JustDeleted = False
'reset flag and then do nothing

Else
If rs.EOF Or Not Me.NewRecord Then
'still don't do anything
Else
With rs
.MoveLast
CurrentNumber = .Fields("serviceticketnbr")
NewNumber = CurrentNumber + 1
Me![ServiceTickNbr] = NewNumber
End With
End If
End If


End Sub

THe same code occurs elsewhere in the database with the same results. The
only difference is that, since this is the current event, the rest of the
form does not load. On other forms, I have a few other options befores it
crashes. The end result is the same - it crashes - but ONLY on my pc. Other
folks in the office are not affected.

If there was a reference problem with the database, wouldn't other users on
other pcs have the same issue? If not, what references am I to be checking?

Thanks for the help. I really do appreciate it.

Don

 

[Guest]

I just read farther down - same issue posted on 10/28/04. When I ran regsvr
last time, I used the DAO350.dll file. Re-running it with DAO360.dll seems
to have fixed the issue. If anyone knows why this problem popped up with my
machine, I am still interested.

Thanks again

Don

Here is the rest of the code for this procedure. It looks for the next
available number in the database when the "Current" event occurs.

Private Sub Form_Current()
Dim rs As Object
Dim NewNumber As Integer
Dim CurrentNumber As Integer

AlreadyAsked = False

Set rs = Me.Recordset.Clone
If JustDeleted Then
JustDeleted = False
'reset flag and then do nothing

Else
If rs.EOF Or Not Me.NewRecord Then
'still don't do anything
Else
With rs
.MoveLast
CurrentNumber = .Fields("serviceticketnbr")
NewNumber = CurrentNumber + 1
Me![ServiceTickNbr] = NewNumber
End With
End If
End If


End Sub

THe same code occurs elsewhere in the database with the same results. The
only difference is that, since this is the current event, the rest of the
form does not load. On other forms, I have a few other options befores it
crashes. The end result is the same - it crashes - but ONLY on my pc. Other
folks in the office are not affected.

If there was a reference problem with the database, wouldn't other users on
other pcs have the same issue? If not, what references am I to be checking?

Thanks for the help. I really do appreciate it.

Don

Can you give us more info about the context of this code step...such as
posting more of the code both before and after it?

Have you checked the references in the database to be sure none are missing?

 

[Ken Snell [MVP]]

If different people are sharing the same database file, then each user's PC
will have its references "imposed" on the database...in other words, if your
PC uses DAO3.5, and another PC is using DAO3.6, then the next time you open
the file, the file will look for DAO3.6.

Another reason why front ends should not be shared, but instead each user
should have his/her own copy of the front end.
--

Ken Snell
<MS ACCESS MVP>

I just read farther down - same issue posted on 10/28/04. When I ran
regsvr
last time, I used the DAO350.dll file. Re-running it with DAO360.dll
seems
to have fixed the issue. If anyone knows why this problem popped up with
my
machine, I am still interested.

Thanks again

Don

Here is the rest of the code for this procedure. It looks for the next
available number in the database when the "Current" event occurs.

Private Sub Form_Current()
Dim rs As Object
Dim NewNumber As Integer
Dim CurrentNumber As Integer

AlreadyAsked = False

Set rs = Me.Recordset.Clone
If JustDeleted Then
JustDeleted = False
'reset flag and then do nothing

Else
If rs.EOF Or Not Me.NewRecord Then
'still don't do anything
Else
With rs
.MoveLast
CurrentNumber = .Fields("serviceticketnbr")
NewNumber = CurrentNumber + 1
Me![ServiceTickNbr] = NewNumber
End With
End If
End If


End Sub

THe same code occurs elsewhere in the database with the same results.
The
only difference is that, since this is the current event, the rest of the
form does not load. On other forms, I have a few other options befores
it
crashes. The end result is the same - it crashes - but ONLY on my pc.
Other
folks in the office are not affected.

If there was a reference problem with the database, wouldn't other users
on
other pcs have the same issue? If not, what references am I to be
checking?

Thanks for the help. I really do appreciate it.

Don

Can you give us more info about the context of this code step...such as
posting more of the code both before and after it?

Have you checked the references in the database to be sure none are
missing?

--

Ken Snell
<MS ACCESS MVP>

I created an application that I was able to use for several months.
Now,
when I start various portions, I get a "Run-Time Error 429 ActiveX
cannot
do
something" error. I have tried re-installing office, running regsvr,
deleting the DAo folder and re-installing everything all over again.
The
application works on other pcs but not mine anymore....

the code is:
Set rs = Me.Recordset.Clone

I tried changing it to
Set rs = dbengine.Me.Recordset.Clone

but that just made another error.

Anyone have any ideas? Please let me know.

 

[Guest]

If each user has their own copy of the front end, then won't each user
essentially have their own database? Or am I missing something? Right now,
this database is located on one pc (shared access - peer-to-peer network) and
everyone has a shortcut to it. That way, everyone can see and manipulate the
same data.

If there is a better way to allow everyone to have access to the same
information without running into this problem?

If different people are sharing the same database file, then each user's PC
will have its references "imposed" on the database...in other words, if your
PC uses DAO3.5, and another PC is using DAO3.6, then the next time you open
the file, the file will look for DAO3.6.

Another reason why front ends should not be shared, but instead each user
should have his/her own copy of the front end.
--

Ken Snell
<MS ACCESS MVP>

I just read farther down - same issue posted on 10/28/04. When I ran
regsvr
last time, I used the DAO350.dll file. Re-running it with DAO360.dll
seems
to have fixed the issue. If anyone knows why this problem popped up with
my
machine, I am still interested.

Thanks again

Don

Here is the rest of the code for this procedure. It looks for the next
available number in the database when the "Current" event occurs.

Private Sub Form_Current()
Dim rs As Object
Dim NewNumber As Integer
Dim CurrentNumber As Integer

AlreadyAsked = False

Set rs = Me.Recordset.Clone
If JustDeleted Then
JustDeleted = False
'reset flag and then do nothing

Else
If rs.EOF Or Not Me.NewRecord Then
'still don't do anything
Else
With rs
.MoveLast
CurrentNumber = .Fields("serviceticketnbr")
NewNumber = CurrentNumber + 1
Me![ServiceTickNbr] = NewNumber
End With
End If
End If


End Sub

THe same code occurs elsewhere in the database with the same results.
The
only difference is that, since this is the current event, the rest of the
form does not load. On other forms, I have a few other options befores
it
crashes. The end result is the same - it crashes - but ONLY on my pc.
Other
folks in the office are not affected.

If there was a reference problem with the database, wouldn't other users
on
other pcs have the same issue? If not, what references am I to be
checking?

Thanks for the help. I really do appreciate it.

Don

:

Can you give us more info about the context of this code step...such as
posting more of the code both before and after it?

Have you checked the references in the database to be sure none are
missing?

--

Ken Snell
<MS ACCESS MVP>

I created an application that I was able to use for several months.
Now,
when I start various portions, I get a "Run-Time Error 429 ActiveX
cannot
do
something" error. I have tried re-installing office, running regsvr,
deleting the DAo folder and re-installing everything all over again.
The
application works on other pcs but not mine anymore....

the code is:
Set rs = Me.Recordset.Clone

I tried changing it to
Set rs = dbengine.Me.Recordset.Clone

but that just made another error.

Anyone have any ideas? Please let me know.

 

[Ken Snell [MVP]]

Yes, what you do is split the database into a backend (contains all the
tables and data) and a frontend (contains queries, forms, reports, etc.).
The backend is placed in a shared folder on your internal network (a folder
that all users can access, with full read/write/create/delete rights), and
then you distribute a copy of the frontend to each user.

The frontend links to the tables in the backend so that the data remain in
the backend only. Thus, each user has his/her own copy of the frontend and
yet all use the same data.

See this information on Tony Toews' web site (Tony is also an ACCESS MVP):
http://www.granite.ab.ca/access/splitapp/index.htm


--

Ken Snell
<MS ACCESS MVP>

If each user has their own copy of the front end, then won't each user
essentially have their own database? Or am I missing something? Right
now,
this database is located on one pc (shared access - peer-to-peer network)
and
everyone has a shortcut to it. That way, everyone can see and manipulate
the
same data.

If there is a better way to allow everyone to have access to the same
information without running into this problem?

If different people are sharing the same database file, then each user's
PC
will have its references "imposed" on the database...in other words, if
your
PC uses DAO3.5, and another PC is using DAO3.6, then the next time you
open
the file, the file will look for DAO3.6.

Another reason why front ends should not be shared, but instead each user
should have his/her own copy of the front end.
--

Ken Snell
<MS ACCESS MVP>

I just read farther down - same issue posted on 10/28/04. When I ran
regsvr
last time, I used the DAO350.dll file. Re-running it with DAO360.dll
seems
to have fixed the issue. If anyone knows why this problem popped up
with
my
machine, I am still interested.

Thanks again

Don

:

Here is the rest of the code for this procedure. It looks for the
next
available number in the database when the "Current" event occurs.

Private Sub Form_Current()
Dim rs As Object
Dim NewNumber As Integer
Dim CurrentNumber As Integer

AlreadyAsked = False

Set rs = Me.Recordset.Clone
If JustDeleted Then
JustDeleted = False
'reset flag and then do nothing

Else
If rs.EOF Or Not Me.NewRecord Then
'still don't do anything
Else
With rs
.MoveLast
CurrentNumber = .Fields("serviceticketnbr")
NewNumber = CurrentNumber + 1
Me![ServiceTickNbr] = NewNumber
End With
End If
End If


End Sub

THe same code occurs elsewhere in the database with the same results.
The
only difference is that, since this is the current event, the rest of
the
form does not load. On other forms, I have a few other options
befores
it
crashes. The end result is the same - it crashes - but ONLY on my pc.
Other
folks in the office are not affected.

If there was a reference problem with the database, wouldn't other
users
on
other pcs have the same issue? If not, what references am I to be
checking?

Thanks for the help. I really do appreciate it.

Don

:

Can you give us more info about the context of this code step...such
as
posting more of the code both before and after it?

Have you checked the references in the database to be sure none are
missing?

--

Ken Snell
<MS ACCESS MVP>

message
I created an application that I was able to use for several months.
Now,
when I start various portions, I get a "Run-Time Error 429 ActiveX
cannot
do
something" error. I have tried re-installing office, running
regsvr,
deleting the DAo folder and re-installing everything all over
again.
The
application works on other pcs but not mine anymore....

the code is:
Set rs = Me.Recordset.Clone

I tried changing it to
Set rs = dbengine.Me.Recordset.Clone

but that just made another error.

Anyone have any ideas? Please let me know.

 

[Guest]

Very cool.

Thanks for the help and tips. I am going to get this stuff figured out one
of these days.....

I'll scream if I need more help.

Yes, what you do is split the database into a backend (contains all the
tables and data) and a frontend (contains queries, forms, reports, etc.).
The backend is placed in a shared folder on your internal network (a folder
that all users can access, with full read/write/create/delete rights), and
then you distribute a copy of the frontend to each user.

The frontend links to the tables in the backend so that the data remain in
the backend only. Thus, each user has his/her own copy of the frontend and
yet all use the same data.

See this information on Tony Toews' web site (Tony is also an ACCESS MVP):
http://www.granite.ab.ca/access/splitapp/index.htm


--

Ken Snell
<MS ACCESS MVP>

If each user has their own copy of the front end, then won't each user
essentially have their own database? Or am I missing something? Right
now,
this database is located on one pc (shared access - peer-to-peer network)
and
everyone has a shortcut to it. That way, everyone can see and manipulate
the
same data.

If there is a better way to allow everyone to have access to the same
information without running into this problem?

If different people are sharing the same database file, then each user's
PC
will have its references "imposed" on the database...in other words, if
your
PC uses DAO3.5, and another PC is using DAO3.6, then the next time you
open
the file, the file will look for DAO3.6.

Another reason why front ends should not be shared, but instead each user
should have his/her own copy of the front end.
--

Ken Snell
<MS ACCESS MVP>



I just read farther down - same issue posted on 10/28/04. When I ran
regsvr
last time, I used the DAO350.dll file. Re-running it with DAO360.dll
seems
to have fixed the issue. If anyone knows why this problem popped up
with
my
machine, I am still interested.

Thanks again

Don

:

Here is the rest of the code for this procedure. It looks for the
next
available number in the database when the "Current" event occurs.

Private Sub Form_Current()
Dim rs As Object
Dim NewNumber As Integer
Dim CurrentNumber As Integer

AlreadyAsked = False

Set rs = Me.Recordset.Clone
If JustDeleted Then
JustDeleted = False
'reset flag and then do nothing

Else
If rs.EOF Or Not Me.NewRecord Then
'still don't do anything
Else
With rs
.MoveLast
CurrentNumber = .Fields("serviceticketnbr")
NewNumber = CurrentNumber + 1
Me![ServiceTickNbr] = NewNumber
End With
End If
End If


End Sub

THe same code occurs elsewhere in the database with the same results.
The
only difference is that, since this is the current event, the rest of
the
form does not load. On other forms, I have a few other options
befores
it
crashes. The end result is the same - it crashes - but ONLY on my pc.
Other
folks in the office are not affected.

If there was a reference problem with the database, wouldn't other
users
on
other pcs have the same issue? If not, what references am I to be
checking?

Thanks for the help. I really do appreciate it.

Don

:

Can you give us more info about the context of this code step...such
as
posting more of the code both before and after it?

Have you checked the references in the database to be sure none are
missing?

--

Ken Snell
<MS ACCESS MVP>

message
I created an application that I was able to use for several months.
Now,
when I start various portions, I get a "Run-Time Error 429 ActiveX
cannot
do
something" error. I have tried re-installing office, running
regsvr,
deleting the DAo folder and re-installing everything all over
again.
The
application works on other pcs but not mine anymore....

the code is:
Set rs = Me.Recordset.Clone

I tried changing it to
Set rs = dbengine.Me.Recordset.Clone

but that just made another error.

Anyone have any ideas? Please let me know.