Visual Dbase 7.01

[EDDIE SHUM]

Hi.

I have developed several applications with Visual Dbase 5.5 and 7. Last
Friday, I have dowloaded 7.01 and have followed the instruction of
BORLAND exactly by removing all the files ending with "o" from my
application and REBUILT ALL.

Now, everytime I try to run my (re-complied) exe file, I am getting the
following message 'Internal error : invalid bytecode ...'. I have tried
on another computer - the same message. But each individual programs,
forms, reports having by now new object file names ending with 'o' works
fine and have the new features of 7.01. This is strange, especially I
did the same thing when I changed my application from 5.5 to 5.6. There
were no problems then.

This morning, I changed the internal clock of my computer from 1998 to
1997 hoping to fool 7.01 and then repeat the process of removing all the
files ending with "o" from my application and REBUILT ALL. It still
doesn't work. The same old message.

Could someone please tell me what did I do wrong?

Also, BORLAND mentioned in their 7.01 README.TXT that in the same
location one can download the updated InstallShield Express. I cannot
find this location. Could someone please tell me where it is?

Please find below extracts of 7.01 ReadMe.txt.

* If you have installed the 7.01 update, be sure to
recompile all object code files. In particular, if you
have run one of the 7.0 sample files for the first time
recently, the compiled object code file may be dated
later than the new 7.01 source code, so the file will not
be automatically recompiled.

For program files in a project, you can use the
Build|Rebuild All menu option to recompile all the
program files. Or you may simply delete all your object
code files. These files have the same extension as the
source code, but with the last letter changed to "O"; for
example, .PRO, .WFO, .CO, and .REO. The next time you run
or load the program file, it will be recompiled
automatically.

* An updated InstallShield Express for Visual dBASE is also
available for downloading, in the same location as the
7.01 update. (Be sure to download the right one:
Professional or Client/Server. The full 7.01 product
already has the latest InstallShield Express -- you do
not have to download it.) After installing the updated
InstallShield Express, you should rebuild your
installation disks, after rebuilding your project in
7.01.

Thank you in advance.

[Ken Mayer]

EDDIE SHUM <econ...@netvigator.com> wrote:

>I have developed several applications with Visual Dbase 5.5 and 7. Last
>Friday, I have dowloaded 7.01 and have followed the instruction of
>BORLAND exactly by removing all the files ending with "o" from my
>application and REBUILT ALL.
>
>Now, everytime I try to run my (re-complied) exe file, I am getting the
>following message 'Internal error : invalid bytecode ...'. I have tried
>on another computer - the same message. But each individual programs,
>forms, reports having by now new object file names ending with 'o' works
>fine and have the new features of 7.01. This is strange, especially I
>did the same thing when I changed my application from 5.5 to 5.6. There
>were no problems then.

Did you check all custom control files? (.CO, .CFO, etc ...)

Ken

---
Ken Mayer (Golden Stag Productions)
http://www.mindspring.com/~hirschv/homepage.htm
Please respond in the newsgroup unless explictly asked otherwise

[Bowen Moursund]

>I have developed several applications with Visual Dbase 5.5 and 7. Last
>Friday, I have dowloaded 7.01 and have followed the instruction of
>BORLAND exactly by removing all the files ending with "o" from my
>application and REBUILT ALL.
>
>Now, everytime I try to run my (re-complied) exe file, I am getting the
>following message 'Internal error : invalid bytecode ...'.

Your test deployment(s) with v7.0 has probably left an old copy of the
runtime engine installed somewhere. Replace it with the 7.01 version of
VDB7RUN.EXE, or remove it.
__
Bowen Moursund (TeamB)
bowen...@nerds.com
http://www.lonestar.texas.net/~moursund
Try these help resources:
http://forumsearch.borland.com:88
http://www.dejanews.com/home_ps.shtml

[Paul Franks (TeamB)]

In article <352986...@netvigator.com>, econ...@netvigator.com
says...

> Now, everytime I try to run my (re-complied) exe file, I am getting the
> following message 'Internal error : invalid bytecode ...'.
>

The only known cause you are likely to find is version problems after
applying the 7.01 upgrade. You're on an executable - did you remember to
redeploy the dBASE components so the virtual machine (vdb7run.exe and a
few other files) seen by your executable is updated?

Try the Win95 'Find' gizmo in the start menu. Look for *.??o which are
older than the day you upgraded, and look for vdb7run.exe which has a
timestamp before March 11, 1998. If you find an old vdb7run you'll
likely find a bunch of other old files in the same place. Redeploy the
full dBASE exe package to fix it.
--
Paul Franks (TeamB)

[EDDIE SHUM]

Problem resolved. Thank you very much. I probably cannot offer you any
assistance in programming, but should you need some information about
our part of the world - ASIA, I will be happy to provide the little I
know.

Take care and good luck.

Eddie

[Don Wellsand]

I am having the same problem: internal error: invalid byte code file:
c:\po\po.wfo. I did the following:

1) Deleted all files with ??o in my po and custom directories.
2) Checked vdb7run.exe for 3/11/98 date.
3) Recompiled using build all feature. (get error)
4) Uninstalled 7.01 and reinstalled 7.00 (exe works fine here).
5) Deleted all files with ??o again.
6) Installed 7.01.
7) Verified that vdb7run.exe was 3/11/98.
8) Recompiled using build all feature.

And still received the error. Am I missing something?

Don

[Romain Strieff [TeamB]]

In article <6h3cll$6q...@forums.borland.com>, smar...@mtsgrinders.com
grudgingly admits...

You have to replace the old runtime in the \WINDOWS\SYSTEM too.
--
Romain Strieff [TeamB]
Want quick help? Check previous Q and A at:
http://forumsearch.borland.com:88/ and TIs at
http://www.borland.com/VdBASE/vdbprod.html

[Don Wellsand]

Thanks Romain - You came through again. Now I can get on with the rest of my
life.

Don

Romain Strieff [TeamB] wrote in message ...

[Romain Strieff [TeamB]]

In article <6h4r4i$8l...@forums.borland.com>, smar...@mtsgrinders.com
grudgingly admits...

> Thanks Romain - You came through again. Now I can get on with the rest of my
> life.
>

LOL, I guess this is a success report then.<G>

[Andrew Knight]

Thanks Bowen. Found the version 7 runtime engine in \windows\system and
deleted it - now working fine. Maybe Borland should take note and ensure
that their updates remove old files properly.

Andrew Knight (Botswana!)

[Paul Franks (TeamB)]

In article <6i6she$cj...@forums.borland.com>, akn...@global.bw says...

> Found the version 7 runtime engine in \windows\system and
> deleted it - now working fine. Maybe Borland should take note and ensure
> that their updates remove old files properly.
>

Maybe I should point out that _you_ put it there when _you_ deployed the
app :) The patch is designed to update Borland's product, not yours.
The correct upgrader for deployed apps is a re=deploy of your app with
all its support files. If the replace fails then, that's a bug IMO.

Unfortunately it is almost impossible to guarantee a patch release will
detect every instance of installed software unless it does a file by file
search through every drive. This brings the risk it will go out to
shared network files where you may not want automated replacement.
--
Paul Franks (TeamB)