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

Groups > comp.lang.basic.visual.misc > #1888 > unrolled thread

Which Hardcore Black Belt Ninja PowerVB tricks to avoid at all costs?

Back to article view | Back to comp.lang.basic.visual.misc

Contents

  Which Hardcore Black Belt Ninja PowerVB tricks to avoid at all costs? "Nobody in particular" <nobody@nowhere.INVALID> - 2013-10-07 17:01 -0700
    Re: Which Hardcore Black Belt Ninja PowerVB tricks to avoid at all costs? "Mayayana" <mayayana@invalid.nospam> - 2013-10-07 20:06 -0400
      Re: Which Hardcore Black Belt Ninja PowerVB tricks to avoid at all costs? "Nobody in particular" <nobody@nowhere.INVALID> - 2013-10-11 13:04 -0700
        Re: Which Hardcore Black Belt Ninja PowerVB tricks to avoid at all costs? "Mayayana" <mayayana@invalid.nospam> - 2013-10-11 18:07 -0400
        Re: Which Hardcore Black Belt Ninja PowerVB tricks to avoid at all costs? Tony Toews <ttoews@telusplanet.net> - 2013-10-21 17:42 -0600

#1888 — Which Hardcore Black Belt Ninja PowerVB tricks to avoid at all costs?

Remember the late 90s when "Black Belt" ninja hardcore power VB COM API tricks were all the rage?
Which ones screwed you over bad when it came time to get your code working with Windows 7 and 8?

I'm getting the sinking feeling that the "It just works" runtime support crap really only applies
to the sample code in the tutorials, minus anything having to do with the supplied broken controls
and that it really would be easier to just rewrite everything in Python, Lazarus, or Ruby on Rails.

[toc] | [next] | [standalone]

#1889

| Remember the late 90s when "Black Belt" ninja hardcore power VB COM API 
tricks were all the rage?
| Which ones screwed you over bad when it came time to get your code working 
with Windows 7 and 8?
|

     The only problems I know of with Windows Vista/7/8 are
with inline assembly code that conflicts with DEP. Executable
code from data memory doesn't work. But there are workarounds
even for that. VB6 is still the most widely suppoerted tool
on Windows.

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

#1891

"Mayayana" <mayayana@invalid.nospam> wrote in message news:l2vice$t15$1@dont-email.me...

>| Remember the late 90s when "Black Belt" ninja hardcore power VB COM API
> tricks were all the rage?
> | Which ones screwed you over bad when it came time to get your code working
> with Windows 7 and 8?
> |
>
>     The only problems I know of with Windows Vista/7/8 are
> with inline assembly code that conflicts with DEP. Executable
> code from data memory doesn't work. But there are workarounds
> even for that. VB6 is still the most widely suppoerted tool
> on Windows.

Thanks. I'm looking at a mixed Access 97 and Visual Basic 5.0 project that's
been working fine on Windows XP Pro and apparently hasn't even been changed
or recompiled in the last ten years. I'm worried about possible issues in
migrating it to Windows 7 or 8.1 when Microsoft finally drops support for XP
in April. Is there a writeup anywhere for the current best practices for
"Classic" VB? The last time I did any serious work with VB 5/6, there were
issues with how Class_Terminate events interacted with error handling. Have
these been fixed, or are there commonly accepted workarounds? Will Access 97
and VB5 code work in Win7/8, or do I need to migrate to a newer version of
Access and VB6 or possibly some other language and database engine?

Thanks again.

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

#1892

   I don't use MS Office. Maybe someone else will
address that. With VB5 you'll need to ship the runtime.

  Why not just try installing it on Win7 and see
how it runs? 

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

#1893

On Fri, 11 Oct 2013 13:04:44 -0700, "Nobody in particular"
<nobody@nowhere.INVALID> wrote:
  
> Will Access 97
>and VB5 code work in Win7/8, 

I have no idea why someone wouldn't upgrade the A97 app to Access
2010.   That shouldn't take much work.  Leave everything in MDBs. Just
convert to Access 2010 and see what fails.

Tony

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.basic.visual.misc

csiph-web