64 Bit Vista - MAV on Modi Comm

[Bob Buchanan]

Have my app working OK with 32 bit Vista. But now the calls from clients
having just purchased 64 bit machines are starting.

Have recently loaded 64-bit Vista Home Premium w/SP-1 and all updates on one
of my desktops (w/2gb of ram) - and have Vista 32-bit on a laptop to test
the two installs. The 64-bit version runs noticeably slower and the screens
sorta flutter as they present themselves. With just my app running, am using
only about 32% of available ram.

But the main problem I am having is that when I open the Modi Comm editor I
receive a Memory Access Violation error. If I open a form, I also get the
same message. If I click Ignore, I can work on the form but cannot access
any of the forms source code w/o the MAV error.

This began while using latest download of Version 2.61.5, so I uninstalled
and reloaded 2.61.0. Modi Comm works OK in that version. I also tried with
2.61.4 and that chokes as well. I do not want to use Versions point 2 or 3
because I am not able to set the foreground color of Rectangles, Check
Boxes, or Radio Buttons to any color other than black. So have not tested
those versions.

I tried setting the default editor to Wordpad -- and that works OK. But
would hate to have to use that as my standard editor.

Questions:
Is this Modi Comm Editor Memory Access Violation error a known bug w/64-bit
Vista?
What other editor that is dBASE friendly can I use as a work a round.

Thanks!

Bob Buchanan
www.rvspacemanager.com

[Geoff Wass [dBVIPS]]

Post by Bob Buchanan
Have my app working OK with 32 bit Vista. But now the calls from clients
having just purchased 64 bit machines are starting.
Have recently loaded 64-bit Vista Home Premium w/SP-1 and all updates on one
of my desktops (w/2gb of ram) - and have Vista 32-bit on a laptop to test
the two installs. The 64-bit version runs noticeably slower and the screens
sorta flutter as they present themselves. With just my app running, am using
only about 32% of available ram.
But the main problem I am having is that when I open the Modi Comm editor I
receive a Memory Access Violation error. If I open a form, I also get the
same message. If I click Ignore, I can work on the form but cannot access
any of the forms source code w/o the MAV error.
This began while using latest download of Version 2.61.5, so I uninstalled
and reloaded 2.61.0. Modi Comm works OK in that version. I also tried with
2.61.4 and that chokes as well. I do not want to use Versions point 2 or 3
because I am not able to set the foreground color of Rectangles, Check
Boxes, or Radio Buttons to any color other than black. So have not tested
those versions.
I tried setting the default editor to Wordpad -- and that works OK. But
would hate to have to use that as my standard editor.
Is this Modi Comm Editor Memory Access Violation error a known bug w/64-bit
Vista?
What other editor that is dBASE friendly can I use as a work a round.
Thanks!
Bob Buchanan
www.rvspacemanager.com

Bob,

At this time, dBASE is not certified on 64-bit operating systems. Other
users have experimented with Vista-64 and found a few different problems
with the dBASE IDE. I don't recall what they reported, so your problem
with the source editor may or may not be known to dBI.

[Ken Mayer [dBVIPS]]

Post by Geoff Wass [dBVIPS]

Post by Bob Buchanan
Have my app working OK with 32 bit Vista. But now the calls from clients
having just purchased 64 bit machines are starting.
Have recently loaded 64-bit Vista Home Premium w/SP-1 and all updates on one
of my desktops (w/2gb of ram) - and have Vista 32-bit on a laptop to test
the two installs. The 64-bit version runs noticeably slower and the screens
sorta flutter as they present themselves. With just my app running, am using
only about 32% of available ram.
But the main problem I am having is that when I open the Modi Comm editor I
receive a Memory Access Violation error. If I open a form, I also get the
same message. If I click Ignore, I can work on the form but cannot access
any of the forms source code w/o the MAV error.
This began while using latest download of Version 2.61.5, so I uninstalled
and reloaded 2.61.0. Modi Comm works OK in that version. I also tried with
2.61.4 and that chokes as well. I do not want to use Versions point 2 or 3
because I am not able to set the foreground color of Rectangles, Check
Boxes, or Radio Buttons to any color other than black. So have not tested
those versions.
I tried setting the default editor to Wordpad -- and that works OK. But
would hate to have to use that as my standard editor.
Is this Modi Comm Editor Memory Access Violation error a known bug w/64-bit
Vista?
What other editor that is dBASE friendly can I use as a work a round.
Thanks!
Bob Buchanan
www.rvspacemanager.com

Bob,
At this time, dBASE is not certified on 64-bit operating systems. Other
users have experimented with Vista-64 and found a few different problems
with the dBASE IDE. I don't recall what they reported, so your problem
with the source editor may or may not be known to dBI.

It's my understanding that you can run dBASE under 32-bit compatibility
mode, but I don't have 64-bit, so can't test.

Ken
--
/(Opinions expressed are purely my own, not those of dataBased
Intelligence, Inc.)/

*Ken Mayer* [dBVIPS]
/Golden Stag Productions/
dBASE at goldenstag dot net
http://www.goldenstag.net/GSP
http://www.goldenstag.net/dbase/dBASEBooks.htm
http://www.goldenstag.net/dbase

[Bob Buchanan]

Thank you, Geoff and Ken:

Yep -- I read that on the dBI site, but thought dBI or someone might have a
simple fix. Was told when I upgraded to V64 that 4gb ram is recommended so
perhaps that is causing the MAV. As noted tho, am only seeing about a third
of my 2gb being used. This is what I have done so far:

o Upgraded ram on one of my desktops to 2gb and put in a new Sata 500g
drive. I then gave myself 2, 30g partitions plus a huge third of 320 for
programs and data.

o I then loaded my copy of XP Pro in vol I, and then Vista 64 in vol II -
and now dual boot between the two. (The drive was $79 and the OEM Vist64 was
$119 at Fry's Electronics in Roseville, CA).

o After messing around with the different versions, decided to go with the
latest (Version 2.61.5) of dB PLUS - considering the trade offs that I have
encountered.

o This was my first dual boot so was pleased that it all worked --
considering the tales of woe I had been hearing. Most articles I read
suggested loading XP first in Vol I. -- so that's how I proceeded A couple
of strange things (to me) then happen -- one is that the booted OS always
becomes Drive C: Secondly, when Vista 64 loads, it creates both a Program
Files folder and a Program Files (x86) folder. It then recognizes a 32 bit
program (such as dB PLUS) and loads it automatically in the (x86) folder --
whereas only 64 bit programs go into the Vista 64 Program Files folder.

Originally I had thought of loading Vista64 programs in a 4th partition --
but when I discovered the Program Files (x86) folder -- decided to stay with
loading them in the same drive with Vista64.

o Over the last few days I have been accessing the same source code on my
VOL III (E: drive) from my PLUS package in XP, and then from my PLUS package
from Vista64. Today I started the routine of testing and such while in XP
(as Modi Comm works OK there), then when it runs OK, I run the same module
from Vista64.

o Am first working with the Demo Version of my app -- cause that's the one I
am sending to potential clients and need to get up and running. So far, the
only problems with the program itself are (as mentioned in my last post), it
is running slower in Vista64 and the screens do not paint as sharply as when
running on the XP side. Hope I can get that cleared up because would hate to
put my app out that way. Perhaps more ram and better video card.

o As to deployment -- am sorry to say that it appears IS is not going to run
in Vista64, so am forced to bite the bullet and learn Inno. Ken, have
already downloaded your excellent article to get started (thank you)! I
have downloaded the compiler and Wizard from the authors site and loaded
successfully under the Program Files (x86) Vista folder. I placed limited
lines in a test script and am happy to report it appears to execute
properly.

Anyway -- the only glitch so far is the Modi Comm source editor thing -- and
I can get around that for now with XP Pro just a partition away..

Thanks again . . .

Bob Buchanan
www.rvspacemanager.com

Post by Geoff Wass [dBVIPS]

Post by Bob Buchanan
Have my app working OK with 32 bit Vista. But now the calls from clients
having just purchased 64 bit machines are starting.
Have recently loaded 64-bit Vista Home Premium w/SP-1 and all updates on one
of my desktops (w/2gb of ram) - and have Vista 32-bit on a laptop to test
the two installs. The 64-bit version runs noticeably slower and the screens
sorta flutter as they present themselves. With just my app running, am using
only about 32% of available ram.
But the main problem I am having is that when I open the Modi Comm editor I
receive a Memory Access Violation error. If I open a form, I also get the
same message. If I click Ignore, I can work on the form but cannot access
any of the forms source code w/o the MAV error.
This began while using latest download of Version 2.61.5, so I uninstalled
and reloaded 2.61.0. Modi Comm works OK in that version. I also tried with
2.61.4 and that chokes as well. I do not want to use Versions point 2 or 3
because I am not able to set the foreground color of Rectangles, Check
Boxes, or Radio Buttons to any color other than black. So have not tested
those versions.
I tried setting the default editor to Wordpad -- and that works OK. But
would hate to have to use that as my standard editor.
Is this Modi Comm Editor Memory Access Violation error a known bug w/64-bit
Vista?
What other editor that is dBASE friendly can I use as a work a round.
Thanks!
Bob Buchanan
www.rvspacemanager.com

Bob,
At this time, dBASE is not certified on 64-bit operating systems. Other
users have experimented with Vista-64 and found a few different problems
with the dBASE IDE. I don't recall what they reported, so your problem
with the source editor may or may not be known to dBI.
--
Geoff Wass [dBVIPS]
Montréal, Québec, Canada
.|.|.| dBASE info at http://geocities.com/geoff_wass |.|.|.
.|.|.| ---------------------------------------------------------- |.|.|.
.|.|.| IT Consultant http://Geoff_Wass.com |.|.|.

[Geoff Wass [dBVIPS]]

Post by Bob Buchanan
Yep -- I read that on the dBI site, but thought dBI or someone might have a
simple fix. Was told when I upgraded to V64 that 4gb ram is recommended so
perhaps that is causing the MAV. As noted tho, am only seeing about a third
o Upgraded ram on one of my desktops to 2gb and put in a new Sata 500g
drive. I then gave myself 2, 30g partitions plus a huge third of 320 for
programs and data.
o I then loaded my copy of XP Pro in vol I, and then Vista 64 in vol II -
and now dual boot between the two. (The drive was $79 and the OEM Vist64 was
$119 at Fry's Electronics in Roseville, CA).
o After messing around with the different versions, decided to go with the
latest (Version 2.61.5) of dB PLUS - considering the trade offs that I have
encountered.
o This was my first dual boot so was pleased that it all worked --
considering the tales of woe I had been hearing. Most articles I read
suggested loading XP first in Vol I. -- so that's how I proceeded A couple
of strange things (to me) then happen -- one is that the booted OS always
becomes Drive C: Secondly, when Vista 64 loads, it creates both a Program
Files folder and a Program Files (x86) folder. It then recognizes a 32 bit
program (such as dB PLUS) and loads it automatically in the (x86) folder --
whereas only 64 bit programs go into the Vista 64 Program Files folder.
Originally I had thought of loading Vista64 programs in a 4th partition --
but when I discovered the Program Files (x86) folder -- decided to stay with
loading them in the same drive with Vista64.
o Over the last few days I have been accessing the same source code on my
VOL III (E: drive) from my PLUS package in XP, and then from my PLUS package
from Vista64. Today I started the routine of testing and such while in XP
(as Modi Comm works OK there), then when it runs OK, I run the same module
from Vista64.
o Am first working with the Demo Version of my app -- cause that's the one I
am sending to potential clients and need to get up and running. So far, the
only problems with the program itself are (as mentioned in my last post), it
is running slower in Vista64 and the screens do not paint as sharply as when
running on the XP side. Hope I can get that cleared up because would hate to
put my app out that way. Perhaps more ram and better video card.
o As to deployment -- am sorry to say that it appears IS is not going to run
in Vista64, so am forced to bite the bullet and learn Inno. Ken, have
already downloaded your excellent article to get started (thank you)! I
have downloaded the compiler and Wizard from the authors site and loaded
successfully under the Program Files (x86) Vista folder. I placed limited
lines in a test script and am happy to report it appears to execute
properly.
Anyway -- the only glitch so far is the Modi Comm source editor thing -- and
I can get around that for now with XP Pro just a partition away..
Thanks again . . .
Bob Buchanan
www.rvspacemanager.com

Bob,

This is all very interesting and probably useful for dBI to know. It is
good you have the XP partition as a place to work. Inno Setup works well
and is not hard to use. Thanks for sharing this information.

[kathy kolosky]

Hi Bob. The Editor MAV issue is a known issue.
It will probably not be fixed until we have a fully 64bit compatible version
of dBASE.

Thanks, Kathy
QA
dBI

Post by Bob Buchanan
Have my app working OK with 32 bit Vista. But now the calls from clients
having just purchased 64 bit machines are starting.
Have recently loaded 64-bit Vista Home Premium w/SP-1 and all updates on
one of my desktops (w/2gb of ram) - and have Vista 32-bit on a laptop to
test the two installs. The 64-bit version runs noticeably slower and the
screens sorta flutter as they present themselves. With just my app
running, am using only about 32% of available ram.
But the main problem I am having is that when I open the Modi Comm editor
I receive a Memory Access Violation error. If I open a form, I also get
the same message. If I click Ignore, I can work on the form but cannot
access any of the forms source code w/o the MAV error.
This began while using latest download of Version 2.61.5, so I
uninstalled and reloaded 2.61.0. Modi Comm works OK in that version. I
also tried with 2.61.4 and that chokes as well. I do not want to use
Versions point 2 or 3 because I am not able to set the foreground color of
Rectangles, Check Boxes, or Radio Buttons to any color other than black.
So have not tested those versions.
I tried setting the default editor to Wordpad -- and that works OK. But
would hate to have to use that as my standard editor.
Is this Modi Comm Editor Memory Access Violation error a known bug
w/64-bit Vista?
What other editor that is dBASE friendly can I use as a work a round.
Thanks!
Bob Buchanan
www.rvspacemanager.com

[Bob Buchanan]

Thanks, Kathy. Now I won't wonder if my hardware might be the culprit. Hope
the 64 bit version is not in the too distant future.

Bob Buchanan
www.rvspacemanager.com

Post by kathy kolosky
Hi Bob. The Editor MAV issue is a known issue.
It will probably not be fixed until we have a fully 64bit compatible
version of dBASE.
Thanks, Kathy
QA
dBI

Post by Bob Buchanan
Have my app working OK with 32 bit Vista. But now the calls from clients
having just purchased 64 bit machines are starting.
Have recently loaded 64-bit Vista Home Premium w/SP-1 and all updates on
one of my desktops (w/2gb of ram) - and have Vista 32-bit on a laptop to
test the two installs. The 64-bit version runs noticeably slower and the
screens sorta flutter as they present themselves. With just my app
running, am using only about 32% of available ram.
But the main problem I am having is that when I open the Modi Comm editor
I receive a Memory Access Violation error. If I open a form, I also get
the same message. If I click Ignore, I can work on the form but cannot
access any of the forms source code w/o the MAV error.
This began while using latest download of Version 2.61.5, so I
uninstalled and reloaded 2.61.0. Modi Comm works OK in that version. I
also tried with 2.61.4 and that chokes as well. I do not want to use
Versions point 2 or 3 because I am not able to set the foreground color
of Rectangles, Check Boxes, or Radio Buttons to any color other than
black. So have not tested those versions.
I tried setting the default editor to Wordpad -- and that works OK. But
would hate to have to use that as my standard editor.
Is this Modi Comm Editor Memory Access Violation error a known bug
w/64-bit Vista?
What other editor that is dBASE friendly can I use as a work a round.
Thanks!
Bob Buchanan
www.rvspacemanager.com