Board index » delphi » De{*word*81} doesn't stop in Table events

De{*word*81} doesn't stop in Table events

Hi,

When I debugg my application I can't get the de{*word*81} to halt in any kind of
table avent such as "Before Post", "After Post" e.t.c.
The de{*word*81} stops and work correct in every othe functions and procedure in
the app.

/Ronny

 

Re:De{*word*81} doesn't stop in Table events


Are you saying that if you set a breakpoint in a table event handler the BDE
ignores the breakpoint? I have no problem debugging in table related event
handlers in D6 or any prior version.

--
Bill
(TeamB cannot answer questions received via email)

Re:De{*word*81} doesn't stop in Table events


Bill,

Yes thats correct.
I never had this problem before, but for I while I have this behaiviour and
I can't put my finger on why.
Could it be some settings in the BDE Admin or somewhere else?
I'm acting as an end-user when I ask myself what I have done - Nothing.

/Ronny

"Bill Todd (TeamB)" <bill_nos...@dbginc.com> skrev i meddelandet
news:3c59619d_1@dnews...

Quote
> Are you saying that if you set a breakpoint in a table event handler the
BDE
> ignores the breakpoint? I have no problem debugging in table related event
> handlers in D6 or any prior version.

> --
> Bill
> (TeamB cannot answer questions received via email)

Re:De{*word*81} doesn't stop in Table events


In article <3c5964b0_2@dnews>, ronny.bengts...@robe.se says...

Quote
> Bill,

> Yes thats correct.
> I never had this problem before, but for I while I have this behaiviour and
> I can't put my finger on why.
> Could it be some settings in the BDE Admin or somewhere else?

        The BDE has no control whatsoever over breakpoints.  It's entirely
up to Delphi.  Usually when someone has breakpoints that don't trigger
(or show as disabled while the program is running under the IDE) they
have multiple copies of their source file in different directories.  The
IDE is using one, the compiler the other.

        HTH,

        -Craig

--
 Craig Stuntz (TeamB) Vertex Systems Corp. Columbus, OH
     Delphi/InterBase WebLog: http://delphi.weblogs.com
     InterBase PLANalyzer (Free IB optimization tool):
          http://delphi.weblogs.com/IBPLANalyzer

Re:De{*word*81} doesn't stop in Table events


I think Craig has right. Put some reporting code in event handling
procedure.

Regards Tomi

Re:De{*word*81} doesn't stop in Table events


Craig,

That's sounds scary.
We and I think a lot of other users have copies of theirs sourcefiles in
different directories for backup purposes
How can we check what path the compiler and de{*word*81} use?

/Ronny

"Craig Stuntz" <cstuntz@no_spam.vertexsoftware.com> skrev i meddelandet
news:MPG.16c3420666a229479897ec@newsgroups.borland.com...

Quote
> In article <3c5964b0_2@dnews>, ronny.bengts...@robe.se says...
> > Bill,

> > Yes thats correct.
> > I never had this problem before, but for I while I have this behaiviour
and
> > I can't put my finger on why.
> > Could it be some settings in the BDE Admin or somewhere else?

> The BDE has no control whatsoever over breakpoints.  It's entirely
> up to Delphi.  Usually when someone has breakpoints that don't trigger
> (or show as disabled while the program is running under the IDE) they
> have multiple copies of their source file in different directories.  The
> IDE is using one, the compiler the other.

> HTH,

> -Craig

> --
>  Craig Stuntz (TeamB) Vertex Systems Corp. Columbus, OH
>      Delphi/InterBase WebLog: http://delphi.weblogs.com
>      InterBase PLANalyzer (Free IB optimization tool):
>           http://delphi.weblogs.com/IBPLANalyzer

Re:De{*word*81} doesn't stop in Table events


In article <3c598f08$1_1@dnews>, ronny.bengts...@robe.se says...

Quote

> That's sounds scary.
> We and I think a lot of other users have copies of theirs sourcefiles in
> different directories for backup purposes
> How can we check what path the compiler and de{*word*81} use?

        The easiest way is to make sure there's no possible way for the
compiler to find the wrong source files.  IMHO, the best way to do this
is to back up your code to a version control system, not to a directory
somewhere.  I strongly recommend use of a version control system on
*any* commercial software project.  Since there are good, free systems
available which integrate with Delphi, there's really no excuse not to
use one.

        This way you only ever have one copy of a particular file on your
machine at a time, and you can be certain that it's the correct version.  
Back versions are always available should you need them.

        But if you must keep copies in alternate directories, look at your
project search path in project->options, and your global library path in
Environment options.  Check your paths in the DPR file.  Analyze any
relative paths in your source or options dialogs and make sure they're
really going where you think they are.

        HTH,

        -Craig

--
 Craig Stuntz (TeamB) Vertex Systems Corp. Columbus, OH
     Delphi/InterBase WebLog: http://delphi.weblogs.com
     InterBase PLANalyzer (Free IB optimization tool):
          http://delphi.weblogs.com/IBPLANalyzer

Re:De{*word*81} doesn't stop in Table events


Craig,

Yes, we are using version control systems (MS Sourcesafe) but it sometimes
easier to just copy to and from a directory.
I thought that if you had the path in the Project Manager correct you would
be safe.
I will follow your suggestions and check my path.

Thanks

/Ronny

"Craig Stuntz" <cstuntz@no_spam.vertexsoftware.com> skrev i meddelandet
news:MPG.16c3843fd0d04c49897f2@newsgroups.borland.com...

Quote
> In article <3c598f08$1_1@dnews>, ronny.bengts...@robe.se says...

> > That's sounds scary.
> > We and I think a lot of other users have copies of theirs sourcefiles in
> > different directories for backup purposes
> > How can we check what path the compiler and de{*word*81} use?

> The easiest way is to make sure there's no possible way for the
> compiler to find the wrong source files.  IMHO, the best way to do this
> is to back up your code to a version control system, not to a directory
> somewhere.  I strongly recommend use of a version control system on
> *any* commercial software project.  Since there are good, free systems
> available which integrate with Delphi, there's really no excuse not to
> use one.

> This way you only ever have one copy of a particular file on your
> machine at a time, and you can be certain that it's the correct version.
> Back versions are always available should you need them.

> But if you must keep copies in alternate directories, look at your
> project search path in project->options, and your global library path in
> Environment options.  Check your paths in the DPR file.  Analyze any
> relative paths in your source or options dialogs and make sure they're
> really going where you think they are.

> HTH,

> -Craig

> --
>  Craig Stuntz (TeamB) Vertex Systems Corp. Columbus, OH
>      Delphi/InterBase WebLog: http://delphi.weblogs.com
>      InterBase PLANalyzer (Free IB optimization tool):
>           http://delphi.weblogs.com/IBPLANalyzer

Re:De{*word*81} doesn't stop in Table events


Also check the paths in the project file. I have seen cases where one unit
was listed in the uses clause in the project file with a full path to
another directory while all other units had no path and were using the copy
in the project directory.

--
Bill
(TeamB cannot answer questions received via email)

Re:De{*word*81} doesn't stop in Table events


Bill,

Yes, we have checked all our path and they was correct.
I can see a similiar problem in  borland.public.delphi.ide from John
Kaufmann "De{*word*81} Problem" this task is not answered yet.

/Ronny

"Bill Todd (TeamB)" <bill_nos...@dbginc.com> skrev i meddelandet
news:3c59d4ee_1@dnews...

Quote
> Also check the paths in the project file. I have seen cases where one unit
> was listed in the uses clause in the project file with a full path to
> another directory while all other units had no path and were using the
copy
> in the project directory.

> --
> Bill
> (TeamB cannot answer questions received via email)

Re:De{*word*81} doesn't stop in Table events


You have the handler defined, but are you sure it's being called?  When you
build it (assuming D5), do you get the little blue dots beside each line?
Are you sure that the handler has been assigned to a table event (check the
TTable events in the Object Inspector).

I've coded handlers in the past and set breakpoints only to find that the
event doesn't fire.  Call the event "manually" (i.e. inside a TButton event,
for example).

Rob

Quote
"Ronny Bengtsson" <ronny.bengts...@robe.se> wrote in message

news:3c5a979b_2@dnews...
Quote
> Bill,

> Yes, we have checked all our path and they was correct.
> I can see a similiar problem in  borland.public.delphi.ide from John
> Kaufmann "De{*word*81} Problem" this task is not answered yet.

> /Ronny

> "Bill Todd (TeamB)" <bill_nos...@dbginc.com> skrev i meddelandet
> news:3c59d4ee_1@dnews...
> > Also check the paths in the project file. I have seen cases where one
unit
> > was listed in the uses clause in the project file with a full path to
> > another directory while all other units had no path and were using the
> copy
> > in the project directory.

> > --
> > Bill
> > (TeamB cannot answer questions received via email)

Re:De{*word*81} doesn't stop in Table events


Rob,

No I DON'T get the blue dot on the particular Unit (Datamodule).
I have removed the unit from the project and added it again but no blue dot
at all.
I also have removed all DCU files and rebiuld it without success.
I also have checked the TTable events.
I can see in my library the changes to the Unit  has been done and I have
the blue dot on the rest of the units.
This unit is an datamodule with 45 TTables on it.

How can I be sure that all units has been rebuild?

/Ronny

"Robby Tanner" <rtan...@cls.usask.ca> skrev i meddelandet
news:3c5ab691_2@dnews...

Quote
> You have the handler defined, but are you sure it's being called?  When
you
> build it (assuming D5), do you get the little blue dots beside each line?
> Are you sure that the handler has been assigned to a table event (check
the
> TTable events in the Object Inspector).

> I've coded handlers in the past and set breakpoints only to find that the
> event doesn't fire.  Call the event "manually" (i.e. inside a TButton
event,
> for example).

> Rob

> "Ronny Bengtsson" <ronny.bengts...@robe.se> wrote in message
> news:3c5a979b_2@dnews...
> > Bill,

> > Yes, we have checked all our path and they was correct.
> > I can see a similiar problem in  borland.public.delphi.ide from John
> > Kaufmann "De{*word*81} Problem" this task is not answered yet.

> > /Ronny

> > "Bill Todd (TeamB)" <bill_nos...@dbginc.com> skrev i meddelandet
> > news:3c59d4ee_1@dnews...
> > > Also check the paths in the project file. I have seen cases where one
> unit
> > > was listed in the uses clause in the project file with a full path to
> > > another directory while all other units had no path and were using the
> > copy
> > > in the project directory.

> > > --
> > > Bill
> > > (TeamB cannot answer questions received via email)

Re:De{*word*81} doesn't stop in Table events


It appears we're getting somewhere.

You look for the little blue dots in the "margin" (the same place where the
red dots show up when you set breakpoints) of the unit itself.  They appear
to the left of the lines of code after a successful build or compile.  Do
you get blue dots beside any lines in the datamodule?
As mentioned previously, it appears the wrong datamodule is being used.

As for making sure all the units are being built, Project | Build All should
do it.

Rob

Quote
"Ronny Bengtsson" <ronny.bengts...@robe.se> wrote in message

news:3c5abf72_1@dnews...
Quote
> Rob,

> No I DON'T get the blue dot on the particular Unit (Datamodule).
> I have removed the unit from the project and added it again but no blue
dot
> at all.
> I also have removed all DCU files and rebiuld it without success.
> I also have checked the TTable events.
> I can see in my library the changes to the Unit  has been done and I have
> the blue dot on the rest of the units.
> This unit is an datamodule with 45 TTables on it.

> How can I be sure that all units has been rebuild?

> /Ronny

> "Robby Tanner" <rtan...@cls.usask.ca> skrev i meddelandet
> news:3c5ab691_2@dnews...
> > You have the handler defined, but are you sure it's being called?  When
> you
> > build it (assuming D5), do you get the little blue dots beside each
line?
> > Are you sure that the handler has been assigned to a table event (check
> the
> > TTable events in the Object Inspector).

> > I've coded handlers in the past and set breakpoints only to find that
the
> > event doesn't fire.  Call the event "manually" (i.e. inside a TButton
> event,
> > for example).

> > Rob

> > "Ronny Bengtsson" <ronny.bengts...@robe.se> wrote in message
> > news:3c5a979b_2@dnews...
> > > Bill,

> > > Yes, we have checked all our path and they was correct.
> > > I can see a similiar problem in  borland.public.delphi.ide from John
> > > Kaufmann "De{*word*81} Problem" this task is not answered yet.

> > > /Ronny

> > > "Bill Todd (TeamB)" <bill_nos...@dbginc.com> skrev i meddelandet
> > > news:3c59d4ee_1@dnews...
> > > > Also check the paths in the project file. I have seen cases where
one
> > unit
> > > > was listed in the uses clause in the project file with a full path
to
> > > > another directory while all other units had no path and were using
the
> > > copy
> > > > in the project directory.

> > > > --
> > > > Bill
> > > > (TeamB cannot answer questions received via email)

Re:De{*word*81} doesn't stop in Table events


Rob,

Yes, I have localised where to find  the blue dots.
I have them in all other units but not in this particular datamodule.
I have tried to Build All but no blue dots appear in that unit
Obvious this unit is used because when I drop a new TTable and TDatasource
on it and drop a button and DBEditfield on the main form connected to the
new table everything works as expected.
The only blue dot I can see to the left hand in that unit is at the last
line (end.)

/Ronny

"Robby Tanner" <rtan...@cls.usask.ca> skrev i meddelandet
news:3c5ac90d_2@dnews...

Quote
> It appears we're getting somewhere.

> You look for the little blue dots in the "margin" (the same place where
the
> red dots show up when you set breakpoints) of the unit itself.  They
appear
> to the left of the lines of code after a successful build or compile.  Do
> you get blue dots beside any lines in the datamodule?
> As mentioned previously, it appears the wrong datamodule is being used.

> As for making sure all the units are being built, Project | Build All
should
> do it.

> Rob

> "Ronny Bengtsson" <ronny.bengts...@robe.se> wrote in message
> news:3c5abf72_1@dnews...
> > Rob,

> > No I DON'T get the blue dot on the particular Unit (Datamodule).
> > I have removed the unit from the project and added it again but no blue
> dot
> > at all.
> > I also have removed all DCU files and rebiuld it without success.
> > I also have checked the TTable events.
> > I can see in my library the changes to the Unit  has been done and I
have
> > the blue dot on the rest of the units.
> > This unit is an datamodule with 45 TTables on it.

> > How can I be sure that all units has been rebuild?

> > /Ronny

> > "Robby Tanner" <rtan...@cls.usask.ca> skrev i meddelandet
> > news:3c5ab691_2@dnews...
> > > You have the handler defined, but are you sure it's being called?
When
> > you
> > > build it (assuming D5), do you get the little blue dots beside each
> line?
> > > Are you sure that the handler has been assigned to a table event
(check
> > the
> > > TTable events in the Object Inspector).

> > > I've coded handlers in the past and set breakpoints only to find that
> the
> > > event doesn't fire.  Call the event "manually" (i.e. inside a TButton
> > event,
> > > for example).

> > > Rob

> > > "Ronny Bengtsson" <ronny.bengts...@robe.se> wrote in message
> > > news:3c5a979b_2@dnews...
> > > > Bill,

> > > > Yes, we have checked all our path and they was correct.
> > > > I can see a similiar problem in  borland.public.delphi.ide from John
> > > > Kaufmann "De{*word*81} Problem" this task is not answered yet.

> > > > /Ronny

> > > > "Bill Todd (TeamB)" <bill_nos...@dbginc.com> skrev i meddelandet
> > > > news:3c59d4ee_1@dnews...
> > > > > Also check the paths in the project file. I have seen cases where
> one
> > > unit
> > > > > was listed in the uses clause in the project file with a full path
> to
> > > > > another directory while all other units had no path and were using
> the
> > > > copy
> > > > > in the project directory.

> > > > > --
> > > > > Bill
> > > > > (TeamB cannot answer questions received via email)

Re:De{*word*81} doesn't stop in Table events


Copy *.pas and *.dfm to a new location. Define a new project with a new name
and add all units. Rebuild and see if you have all *.dcu.

Or define end test new event (OnCalcFields) to see if it is really working.

Regards Tomi

Go to page: [1] [2]

Other Threads