Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Modules / DAO / VBA / May 2005

Tip: Looking for answers? Try searching our database.

Access 2003 runtime error

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Carla Bradley - 27 Apr 2005 23:25 GMT
I know absolutely nothing about Access, but get to support it. I have a
client that was just upgraded to Access 2003. He has a database that he is
getting a runtime error on all of a sudden. It happens after the delete
confirm event. It says runtime error 2424 - the expression you entered had a
field control or property name that the database cannot find. It worked just
fine in 2002 and they said no changes had been made to it. Any ideas?
Alex Dybenko - 28 Apr 2005 06:04 GMT
Hi,
I think you have to look at code in order to see what it wrong there...
normally both access versions you mention are compatible, but could be some
reference issues, say to Word or Excel, and this can break application.

Signature

Alex Dybenko (MVP)
http://Alex.Dybenko.com
http://www.PointLtd.com

>I know absolutely nothing about Access, but get to support it. I have a
> client that was just upgraded to Access 2003. He has a database that he is
[quoted text clipped - 4 lines]
> just
> fine in 2002 and they said no changes had been made to it. Any ideas?
Carla Bradley - 29 Apr 2005 19:15 GMT
I asked the client and he said this: It looks like what is happening is that
the record is being deleted before it use to be.  The record is valid in the
OnDelete event but is not invalid in the BeforeConfirmDelete event and in the
AfterConfirmDelete event.

> Hi,
> I think you have to look at code in order to see what it wrong there...
[quoted text clipped - 9 lines]
> > just
> > fine in 2002 and they said no changes had been made to it. Any ideas?
Alex Dybenko - 30 Apr 2005 12:31 GMT
Hmm, then it is strange, because both BeforeConfirmDelete and
AfterConfirmDelete occure before Delete event. can you post your code from
these events here?

Signature

Alex Dybenko (MVP)
http://Alex.Dybenko.com
http://www.PointLtd.com

>I asked the client and he said this: It looks like what is happening is
>that
[quoted text clipped - 20 lines]
>> > just
>> > fine in 2002 and they said no changes had been made to it. Any ideas?
Tony Traylor - 04 May 2005 17:54 GMT
I have since changed the code.  I used blobal variables to store my needed
information when the Delete event fired and then used them in the
AfterDeleteConfirm event go get around the problem.

Before, I was using the value of a check box on the subform where the record
was being deleted.  The value of the check box became invalid on the
AfterdeleteConfirm event.  The code was similiar to:

if cboPointsAssigned = True then
         Do something
end if

I also put some message box displays is the Delete, BeforeDeleteConfirm and
the AfterDeleteConfirmEvent and the events fired in the following order:
Delete
BeforeDeleteConfirm
AfterDeleteConfirm

I do not know if this was the order they fired before the upgrade.  If looks
like the record is now becoming invalid before it should.

If you would like to contact me via the phone, my number is (502)627-4192.

Thanks,
Tony

> Hmm, then it is strange, because both BeforeConfirmDelete and
> AfterConfirmDelete occure before Delete event. can you post your code from
[quoted text clipped - 24 lines]
> >> > just
> >> > fine in 2002 and they said no changes had been made to it. Any ideas?
Alex Dybenko - 05 May 2005 07:00 GMT
Hi Tony,
yes, of course you  right, delete occurs before *confirm events,sorry,
messed this with other control.
Anyway - great that you found a workaround

Alex

>I have since changed the code.  I used blobal variables to store my needed
> information when the Delete event fired and then used them in the
[quoted text clipped - 64 lines]
>> >> > fine in 2002 and they said no changes had been made to it. Any
>> >> > ideas?
Tony Traylor - 05 May 2005 16:44 GMT
Why did  this change.  I sould not have had to find a work around.  How can I
be assured this work around will work in the next version?  Will this problem
be fixed?

> Hi Tony,
> yes, of course you  right, delete occurs before *confirm events,sorry,
[quoted text clipped - 71 lines]
> >> >> > fine in 2002 and they said no changes had been made to it. Any
> >> >> > ideas?
Alex Dybenko - 05 May 2005 19:39 GMT
Well, this i dont know, and not sure that somebody can tell you.
also depends on your code...
Signature

Alex Dybenko (MVP)
http://Alex.Dybenko.com
http://www.PointLtd.com

> Why did  this change.  I sould not have had to find a work around.  How
> can I
[quoted text clipped - 86 lines]
>> >> >> > fine in 2002 and they said no changes had been made to it. Any
>> >> >> > ideas?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.