Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.clipper.visual-objects > #642 > unrolled thread

Moving to VO 2.8 from 2.7

Back to article view | Back to comp.lang.clipper.visual-objects

Contents

  Moving to VO 2.8 from 2.7 beth <bethKujala@aol.com> - 2011-04-02 18:43 -0700
    Re: Moving to VO 2.8 from 2.7 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-04-03 12:47 +0200
      Re: Moving to VO 2.8 from 2.7 beth <bethKujala@aol.com> - 2011-04-03 09:47 -0700
        Re: Moving to VO 2.8 from 2.7 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-04-03 23:37 +0200
        Re: Moving to VO 2.8 from 2.7 "Stephen Quinn" <stevejqNO@bigpondSPAM.net.au> - 2011-04-04 10:31 +1000
          Re: Moving to VO 2.8 from 2.7 beth <bethKujala@aol.com> - 2011-04-04 18:23 -0700
            Re: Moving to VO 2.8 from 2.7 "Stephen Quinn" <stevejqNO@bigpondSPAM.net.au> - 2011-04-05 11:46 +1000
              Re: Moving to VO 2.8 from 2.7 beth <bethKujala@aol.com> - 2011-04-05 06:04 -0700
                Re: Moving to VO 2.8 from 2.7 D.J.W. van Kooten <public@ic2remove.this.com> - 2011-04-05 20:18 +0200
                Re: Moving to VO 2.8 from 2.7 "Willie Moore" <williem@wmconsulting.com> - 2011-04-05 14:00 -0500
                  Re: Moving to VO 2.8 from 2.7 beth <bethKujala@aol.com> - 2011-04-05 14:14 -0700
                    Re: Moving to VO 2.8 from 2.7 "Willie Moore" <williem@wmconsulting.com> - 2011-04-05 19:00 -0500
                    Re: Moving to VO 2.8 from 2.7 "Willie Moore" <williem@wmconsulting.com> - 2011-04-06 07:50 -0500
                      Re: Moving to VO 2.8 from 2.7 beth <bethKujala@aol.com> - 2011-04-06 06:33 -0700
            Re: Moving to VO 2.8 from 2.7 "Geoff Schaller" <geoffx@softwarexobjectives.com.au> - 2011-04-05 21:40 +0000

#642 — Moving to VO 2.8 from 2.7

I'm using Windows 7 and VO 2.8.  I've changed security settings on my
app folder to full control for users.  But I don't see voerror.log
anymore?  And I do have runtime errors!  ;-)  Those questions are
coming next.

Thanks,
  Beth

[toc] | [next] | [standalone]

#647

On Sat, 2 Apr 2011 18:43:05 -0700 (PDT), beth <bethKujala@aol.com>
wrote:

>I'm using Windows 7 and VO 2.8.  I've changed security settings on my
>app folder to full control for users.  But I don't see voerror.log
>anymore?  And I do have runtime errors!  ;-)  Those questions are
>coming next.
>
Hello Beth,

The times I was missing the voerror.log I found this to be the result
of using a file function (e.g. StandardFileDialog) after which the
voerror.log was placed in the directory opened in that dialog.

Could that be your problem?

Dick van Kooten

[toc] | [prev] | [next] | [standalone]

#650

Hi Dick, thanks a lot for your reply, I appreciate all help.

Well, I have found the error log, and it's located in \cavo27\bin.
And, it references Version 2.7, Build 1.2730 -- but I've compiled and
created the executable in 2.8.  I run the 2.8 app, but the error is
appended to my old 2.7 error log.  I must be doing something
fundamentally wrong?  Should I not have both 2.7 and 2.8 on the same
machine?

Beth

On Apr 3, 6:47 am, D.J.W. van Kooten <pub...@ic2remove.this.com>
wrote:
> On Sat, 2 Apr 2011 18:43:05 -0700 (PDT), beth <bethKuj...@aol.com>
> wrote:
>
> >I'm using Windows 7 and VO 2.8.  I've changed security settings on my
> >app folder to full control for users.  But I don't see voerror.log
> >anymore?  And I do have runtime errors!  ;-)  Those questions are
> >coming next.
>
> Hello Beth,
>
> The times I was missing the voerror.log I found this to be the result
> of using a file function (e.g. StandardFileDialog) after which the
> voerror.log was placed in the directory opened in that dialog.
>
> Could that be your problem?
>
> Dick van Kooten

[toc] | [prev] | [next] | [standalone]

#651

On Sun, 3 Apr 2011 09:47:54 -0700 (PDT), beth <bethKujala@aol.com>
wrote:

Hello Beth,

>Well, I have found the error log, and it's located in \cavo27\bin.
>And, it references Version 2.7, Build 1.2730 -- but I've compiled and
>created the executable in 2.8.  I run the 2.8 app, but the error is
>appended to my old 2.7 error log.  

I would say that the workdirectory of your application is \cavo27\bin.
Most of us have included some version of Ralph's errorlog, and there
voerror.log is created in CurDrive() + ":\" + CurDir()	+"\". If you
like, you can download a working version of that lib from our site:

www.ic2.com/cavo/errorhandler.zip

and see what happens (just include it in your appliaction and it will
work)

>I must be doing somethingfundamentally wrong?  Should I not have both 2.7 and 2.8 on the same
>machine?

That's no problem at all, although you will soon be working in 2.8
only.

Dick

[toc] | [prev] | [next] | [standalone]

#652

Beth

Check the system/user paths and make sure the 2.8\bin is before the 2.7\bin 
directory.

If you run your app from the IDE the cavo?\bin directory is where your 
error.log goes but as an exe it usually goes into the app directory.

>  Should I not have both 2.7 and 2.8 on the same machine?
Shouldn't matter - I had 2.5 & 2.7 on the same box.

CYA
Steve

[toc] | [prev] | [next] | [standalone]

#669

Thanks very much Steve and Dick, for your replies.  My problem might
be with GridPro3.dll.  I made a HelloWorld without it, and it runs
with no problem.  But as soon as I add GridPro3 to the Libraries, I
get a message saying "The program can't start because VO27SYS.DLL is
missing from your computer."  I've removed cavo27\bin from the system
path environment variable, and I built HelloWorld in 2.8 only.

Would anybody have suggestions?  Thanks very much!

Beth

On Apr 3, 8:31 pm, "Stephen Quinn" <stevej...@bigpondSPAM.net.au>
wrote:
> Beth
>
> Check the system/user paths and make sure the 2.8\bin is before the 2.7\bin
> directory.
>
> If you run your app from the IDE the cavo?\bin directory is where your
> error.log goes but as an exe it usually goes into the app directory.
>
> >  Should I not have both 2.7 and 2.8 on the same machine?
>
> Shouldn't matter - I had 2.5 & 2.7 on the same box.
>
> CYA
> Steve

[toc] | [prev] | [next] | [standalone]

#670

Beth

You need to build the Gridpro DLL with VO2.8 (if you have the source - 
contact Willie).

The error is telling you that the DLL is dependant on VO2.7 runtime.

Like all 3rd party VO libraries/DLLs they need to be compiled by the version 
of VO your using.

CYA
Steve

[toc] | [prev] | [next] | [standalone]

#683

Thank you Steve!  I see what you mean now.  I was re-compiling
the .aef, thinking that was good enough, but I needed to change it
from a library to a .dll, re-compile, and build.  (Correct?)  Did that
but have errors, so I have requested the updated source from Willie.

Thanks so much for your help.

Beth

On Apr 4, 9:46 pm, "Stephen Quinn" <stevej...@bigpondSPAM.net.au>
wrote:
> Beth
>
> You need to build the Gridpro DLL with VO2.8 (if you have the source -
> contact Willie).
>
> The error is telling you that the DLL is dependant on VO2.7 runtime.
>
> Like all 3rd party VO libraries/DLLs they need to be compiled by the version
> of VO your using.
>
> CYA
> Steve

[toc] | [prev] | [next] | [standalone]

#690

On Tue, 5 Apr 2011 06:04:06 -0700 (PDT), beth <bethKujala@aol.com>
wrote:

>Thank you Steve!  I see what you mean now.  

Hello Beth,

You can use DependencyWalker to see which DLL depends on older stuff.
See http://www.dependencywalker.com/.

Dick

[toc] | [prev] | [next] | [standalone]

#691

Glad to see you back Beth!

Regards,
Willie

"beth"  wrote in message 
news:03ec88f4-a6a9-4278-ac4d-83113085a21e@y31g2000vbp.googlegroups.com...

Thank you Steve!  I see what you mean now.  I was re-compiling
the .aef, thinking that was good enough, but I needed to change it
from a library to a .dll, re-compile, and build.  (Correct?)  Did that
but have errors, so I have requested the updated source from Willie.

Thanks so much for your help.

Beth

On Apr 4, 9:46 pm, "Stephen Quinn" <stevej...@bigpondSPAM.net.au>
wrote:
> Beth
>
> You need to build the Gridpro DLL with VO2.8 (if you have the source -
> contact Willie).
>
> The error is telling you that the DLL is dependant on VO2.7 runtime.
>
> Like all 3rd party VO libraries/DLLs they need to be compiled by the 
> version
> of VO your using.
>
> CYA
> Steve 

[toc] | [prev] | [next] | [standalone]

#694

Thanks Willie.  Very glad to see that you're still here!  :-)

"The procedure entry point KBWedControlWindow:dispatch could not be
located in the dynamic link library GridPro3.dll."

Does this ring a bell with anyone?  This is from my HelloWorld app
which does not call any GridPro functions, but which includes the .dll
in the Application Options.

Thanks!

Beth

On Apr 5, 3:00 pm, "Willie Moore" <will...@wmconsulting.com> wrote:
> Glad to see you back Beth!
>
> Regards,
> Willie
>
> "beth"  wrote in message
>
> news:03ec88f4-a6a9-4278-ac4d-83113085a21e@y31g2000vbp.googlegroups.com...
>
> Thank you Steve!  I see what you mean now.  I was re-compiling
> the .aef, thinking that was good enough, but I needed to change it
> from a library to a .dll, re-compile, and build.  (Correct?)  Did that
> but have errors, so I have requested the updated source from Willie.
>
> Thanks so much for your help.
>
> Beth
>
> On Apr 4, 9:46 pm, "Stephen Quinn" <stevej...@bigpondSPAM.net.au>
> wrote:
>
>
>
> > Beth
>
> > You need to build the Gridpro DLL with VO2.8 (if you have the source -
> > contact Willie).
>
> > The error is telling you that the DLL is dependant on VO2.7 runtime.
>
> > Like all 3rd party VO libraries/DLLs they need to be compiled by the
> > version
> > of VO your using.
>
> > CYA
> > Steve- Hide quoted text -
>
> - Show quoted text -

[toc] | [prev] | [next] | [standalone]

#701

Beth,

I have not seen that one before but will be happy to look at it.

Regards,
Willie

"beth"  wrote in message 
news:f7081b33-c78e-4e3e-bb35-2f697a77ba25@d19g2000yql.googlegroups.com...

Thanks Willie.  Very glad to see that you're still here!  :-)

"The procedure entry point KBWedControlWindow:dispatch could not be
located in the dynamic link library GridPro3.dll."

Does this ring a bell with anyone?  This is from my HelloWorld app
which does not call any GridPro functions, but which includes the .dll
in the Application Options.

Thanks!

Beth

On Apr 5, 3:00 pm, "Willie Moore" <will...@wmconsulting.com> wrote:
> Glad to see you back Beth!
>
> Regards,
> Willie
>
> "beth"  wrote in message
>
> news:03ec88f4-a6a9-4278-ac4d-83113085a21e@y31g2000vbp.googlegroups.com...
>
> Thank you Steve!  I see what you mean now.  I was re-compiling
> the .aef, thinking that was good enough, but I needed to change it
> from a library to a .dll, re-compile, and build.  (Correct?)  Did that
> but have errors, so I have requested the updated source from Willie.
>
> Thanks so much for your help.
>
> Beth
>
> On Apr 4, 9:46 pm, "Stephen Quinn" <stevej...@bigpondSPAM.net.au>
> wrote:
>
>
>
> > Beth
>
> > You need to build the Gridpro DLL with VO2.8 (if you have the source -
> > contact Willie).
>
> > The error is telling you that the DLL is dependant on VO2.7 runtime.
>
> > Like all 3rd party VO libraries/DLLs they need to be compiled by the
> > version
> > of VO your using.
>
> > CYA
> > Steve- Hide quoted text -
>
> - Show quoted text - 

[toc] | [prev] | [next] | [standalone]

#719

Beth,

Check your email. The file I sent out the other day, the dll and the 
declaration didn’t agree. I replaced the files with a freshly build dll and 
the error went away. That is what I get for sending you files from my 
autoexported directory instead of my build. when I am testing (from source) 
I don’t reimport the dll declarations each time I make a change. When I get 
ready to release, I clean everything up, make sure the declarations match 
and retest from a clean machine. Sorry to have caused you an inconvenience.

Regards,
Willie

"beth"  wrote in message 
news:f7081b33-c78e-4e3e-bb35-2f697a77ba25@d19g2000yql.googlegroups.com...

Thanks Willie.  Very glad to see that you're still here!  :-)

"The procedure entry point KBWedControlWindow:dispatch could not be
located in the dynamic link library GridPro3.dll."

Does this ring a bell with anyone?  This is from my HelloWorld app
which does not call any GridPro functions, but which includes the .dll
in the Application Options.

Thanks!

Beth

On Apr 5, 3:00 pm, "Willie Moore" <will...@wmconsulting.com> wrote:
> Glad to see you back Beth!
>
> Regards,
> Willie
>
> "beth"  wrote in message
>
> news:03ec88f4-a6a9-4278-ac4d-83113085a21e@y31g2000vbp.googlegroups.com...
>
> Thank you Steve!  I see what you mean now.  I was re-compiling
> the .aef, thinking that was good enough, but I needed to change it
> from a library to a .dll, re-compile, and build.  (Correct?)  Did that
> but have errors, so I have requested the updated source from Willie.
>
> Thanks so much for your help.
>
> Beth
>
> On Apr 4, 9:46 pm, "Stephen Quinn" <stevej...@bigpondSPAM.net.au>
> wrote:
>
>
>
> > Beth
>
> > You need to build the Gridpro DLL with VO2.8 (if you have the source -
> > contact Willie).
>
> > The error is telling you that the DLL is dependant on VO2.7 runtime.
>
> > Like all 3rd party VO libraries/DLLs they need to be compiled by the
> > version
> > of VO your using.
>
> > CYA
> > Steve- Hide quoted text -
>
> - Show quoted text - 

[toc] | [prev] | [next] | [standalone]

#724

Willie, thanks a lot for checking it out so quickly for me.  Got the
files, re-compilied, error is gone!  Thank you!

I have other errors unrelated to GridPro, working on them now.

Beth

On Apr 6, 8:50 am, "Willie Moore" <will...@wmconsulting.com> wrote:
> Beth,
>
> Check your email. The file I sent out the other day, the dll and the
> declaration didn’t agree. I replaced the files with a freshly build dll and
> the error went away. That is what I get for sending you files from my
> autoexported directory instead of my build. when I am testing (from source)
> I don’t reimport the dll declarations each time I make a change. When I get
> ready to release, I clean everything up, make sure the declarations match
> and retest from a clean machine. Sorry to have caused you an inconvenience.
>
> Regards,
> Willie
>
> "beth"  wrote in message
>
> news:f7081b33-c78e-4e3e-bb35-2f697a77ba25@d19g2000yql.googlegroups.com...
>
> Thanks Willie.  Very glad to see that you're still here!  :-)
>
> "The procedure entry point KBWedControlWindow:dispatch could not be
> located in the dynamic link library GridPro3.dll."
>
> Does this ring a bell with anyone?  This is from my HelloWorld app
> which does not call any GridPro functions, but which includes the .dll
> in the Application Options.
>
> Thanks!
>
> Beth
>
> On Apr 5, 3:00 pm, "Willie Moore" <will...@wmconsulting.com> wrote:
>
>
>
> > Glad to see you back Beth!
>
> > Regards,
> > Willie
>
> > "beth"  wrote in message
>
> >news:03ec88f4-a6a9-4278-ac4d-83113085a21e@y31g2000vbp.googlegroups.com...
>
> > Thank you Steve!  I see what you mean now.  I was re-compiling
> > the .aef, thinking that was good enough, but I needed to change it
> > from a library to a .dll, re-compile, and build.  (Correct?)  Did that
> > but have errors, so I have requested the updated source from Willie.
>
> > Thanks so much for your help.
>
> > Beth
>
> > On Apr 4, 9:46 pm, "Stephen Quinn" <stevej...@bigpondSPAM.net.au>
> > wrote:
>
> > > Beth
>
> > > You need to build the Gridpro DLL with VO2.8 (if you have the source -
> > > contact Willie).
>
> > > The error is telling you that the DLL is dependant on VO2.7 runtime.
>
> > > Like all 3rd party VO libraries/DLLs they need to be compiled by the
> > > version
> > > of VO your using.
>
> > > CYA
> > > Steve- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

[toc] | [prev] | [next] | [standalone]

#695

Beth,

You can put the 2.7 runtimes in the same folder as your 2.8 exe. It is 
just a dll like any other.

Geoff



"beth" <bethKujala@aol.com> wrote in message 
news:988f0322-0853-4088-858b-e5ddfa1d7a81@k7g2000yqj.googlegroups.com:

> Thanks very much Steve and Dick, for your replies.  My problem might
> be with GridPro3.dll.  I made a HelloWorld without it, and it runs
> with no problem.  But as soon as I add GridPro3 to the Libraries, I
> get a message saying "The program can't start because VO27SYS.DLL is
> missing from your computer."  I've removed cavo27\bin from the system
> path environment variable, and I built HelloWorld in 2.8 only.
>
> Would anybody have suggestions?  Thanks very much!
>
> Beth
>
> On Apr 3, 8:31 pm, "Stephen Quinn" <stevej...@bigpondSPAM.net.au>
> wrote:
>
> > Beth
> >
> > Check the system/user paths and make sure the 2.8\bin is before the 2.7\bin
> > directory.
> >
> > If you run your app from the IDE the cavo?\bin directory is where your
> > error.log goes but as an exe it usually goes into the app directory.
> >
>
> > >  Should I not have both 2.7 and 2.8 on the same machine?
> >
>
> > Shouldn't matter - I had 2.5 & 2.7 on the same box.
> >
> > CYA
> > Steve

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.clipper.visual-objects

csiph-web