fatal error while building project

Hi Friends

I'm trying to build project and getting fatal error(C5) error and closes
foxpro
the error is.
****
Fatal error: Exception code=C0000005 @ 30/11/2004 04:46:12 PM. Error log
file: C:\Program Files\microsoft visual foxpro 8\vfp8err.log
Called from - build line 191 {e:\vssshadow806\jab\develop\build.prg
e:\vssshadow806\jab\develop\build.fxp}
Called from - vbuild line 100 {e:\vssshadow806\vip\develop\vbuild.prg
e:\vssshadow806\vip\develop\vbuild.fxp}
*****

actual line of code that causing the error is
BUILD PROJECT (lcProjName) &lcCompile FROM (FULLPATH ('main.prg'))

when i opened .err file i see
compiling e:\vssshadow806\vip\tx\tx.mpr

I thought there's problem in the menu so i opened it manually and did
generate menu which was fine.
I tried rebuild again but same error.so this time i excluded menu from project
and now .err file contains something like
compiling e:\vssshadow806\vip\console\getwaiting.prg

I even excluded that prg from project but getting different file name in
.err file.
so i realized the error in .err file is misleading.

is there anyway to trace what causing the fatal error !!
I tried deleting foxuser files and even rebooting the machine to no avail.
Thanks for ur help
--
cheers

Rick
Tue Nov 30 14:30:03 CST 2004

Rajani,
I've seen problems like this when the Project file itself has become =
corrupt - after all it's just a table with memo fields!
Try recreating the project from scratch, or use a backup of these two =
files from before the crashes started.

Rick

"rajani" <rajani@discussions.microsoft.com> wrote in message =
news:E2D31359-BB9C-494F-86C2-7456559C2CD5@microsoft.com...
> Hi Friends
>=20
> I'm trying to build project and getting fatal error(C5) error and =
closes=20
> foxpro=20
> the error is.
> ****
> Fatal error: Exception code=3DC0000005 @ 30/11/2004 04:46:12 PM. Error =
log=20
> file: C:\Program Files\microsoft visual foxpro 8\vfp8err.log
> Called from - build line 191 {e:\vssshadow806\jab\develop\build.prg=20
> e:\vssshadow806\jab\develop\build.fxp}
> Called from - vbuild line 100 =
{e:\vssshadow806\vip\develop\vbuild.prg=20
> e:\vssshadow806\vip\develop\vbuild.fxp}
> *****
>=20
> actual line of code that causing the error is
> BUILD PROJECT (lcProjName) &lcCompile FROM (FULLPATH ('main.prg'))
>=20
> when i opened .err file i see=20
> compiling e:\vssshadow806\vip\tx\tx.mpr
>=20
> I thought there's problem in the menu so i opened it manually and did=20
> generate menu which was fine.
> I tried rebuild again but same error.so this time i excluded menu from =
project
> and now .err file contains something like
> compiling e:\vssshadow806\vip\console\getwaiting.prg
>=20
> I even excluded that prg from project but getting different file name =
in=20
> .err file.
> so i realized the error in .err file is misleading.
>=20
> is there anyway to trace what causing the fatal error !!
> I tried deleting foxuser files and even rebooting the machine to no =
avail.
> Thanks for ur help
> --=20
> cheers

rajani
Tue Nov 30 15:27:02 CST 2004

Hi Rick
That's what we do.we dont have permanent project file.Everytime we recreate
project file while doing build.

what's frustrating is it just crashes when doing build and u dont even know
what program/scx/class caused it.

Rick is there anytool that monitors/records this building process.
Thanks

"Rick Bean" wrote:

> Rajani,
> I've seen problems like this when the Project file itself has become corrupt - after all it's just a table with memo fields!
> Try recreating the project from scratch, or use a backup of these two files from before the crashes started.
>
> Rick
>
> "rajani" <rajani@discussions.microsoft.com> wrote in message news:E2D31359-BB9C-494F-86C2-7456559C2CD5@microsoft.com...
> > Hi Friends
> >
> > I'm trying to build project and getting fatal error(C5) error and closes
> > foxpro
> > the error is.
> > ****
> > Fatal error: Exception code=C0000005 @ 30/11/2004 04:46:12 PM. Error log
> > file: C:\Program Files\microsoft visual foxpro 8\vfp8err.log
> > Called from - build line 191 {e:\vssshadow806\jab\develop\build.prg
> > e:\vssshadow806\jab\develop\build.fxp}
> > Called from - vbuild line 100 {e:\vssshadow806\vip\develop\vbuild.prg
> > e:\vssshadow806\vip\develop\vbuild.fxp}
> > *****
> >
> > actual line of code that causing the error is
> > BUILD PROJECT (lcProjName) &lcCompile FROM (FULLPATH ('main.prg'))
> >
> > when i opened .err file i see
> > compiling e:\vssshadow806\vip\tx\tx.mpr
> >
> > I thought there's problem in the menu so i opened it manually and did
> > generate menu which was fine.
> > I tried rebuild again but same error.so this time i excluded menu from project
> > and now .err file contains something like
> > compiling e:\vssshadow806\vip\console\getwaiting.prg
> >
> > I even excluded that prg from project but getting different file name in
> > .err file.
> > so i realized the error in .err file is misleading.
> >
> > is there anyway to trace what causing the fatal error !!
> > I tried deleting foxuser files and even rebooting the machine to no avail.
> > Thanks for ur help
> > --
> > cheers
>

Anders
Tue Nov 30 16:34:17 CST 2004


"rajani" <rajani@discussions.microsoft.com> wrote in message
news:E957E0A7-0CF0-4924-8167-ACC059468DA5@microsoft.com...
> Hi Rick
> That's what we do.we dont have permanent project file.Everytime we
recreate
> project file while doing build.
>

Do you start with a completely new project file to which yiyu have only
added the startup Main file? VFP will then add files to the project as they
are referenced on the code.

-Anders

rajani
Tue Nov 30 18:45:03 CST 2004

Yes,Anders
That's what we normally do.

Guess what finally we nailed out the problem.
One of our sub folders causing this.
First we renamed the folder(just to exclude files in them from build) and
build went thru fine.
next we renamed back it to original folder name and copied all its contents
(i mean prg,scx etc.,) one after the one and doing build in between.
finally finally we found the prg that causing the error.
If we just exclude that single prg then build is fine.

Interestingly ,we deleted the whole code in that prg but still get error
when we do build !!
Actually there r no syntax errors or anything like that in that prg.we've
been using it for years.
Any ideas what's happening there.
As u know it definetly not with the code in that prg as we blanked out
completely but still get error!!
Thanks

"Anders Altberg" wrote:

>
> "rajani" <rajani@discussions.microsoft.com> wrote in message
> news:E957E0A7-0CF0-4924-8167-ACC059468DA5@microsoft.com...
> > Hi Rick
> > That's what we do.we dont have permanent project file.Everytime we
> recreate
> > project file while doing build.
> >
>
> Do you start with a completely new project file to which yiyu have only
> added the startup Main file? VFP will then add files to the project as they
> are referenced on the code.
>
> -Anders
>
>

Anders
Tue Nov 30 19:35:01 CST 2004

Not a clue, I'm afraid.
-Anders

"rajani" <rajani@discussions.microsoft.com> wrote in message
news:C71465F5-F7E8-4AE0-9F8C-EC98233C650F@microsoft.com...
> Yes,Anders
> That's what we normally do.
> Actually there r no syntax errors or anything like that in that prg.we've
> been using it for years.
> Any ideas what's happening there.
> As u know it definetly not with the code in that prg as we blanked out
> completely but still get error!!
> Thanks
>

Anders
Tue Nov 30 19:39:36 CST 2004

VFP8 has stricter syntax checking. This is illegal in VFP8
LOCAL x,y z, v
Notice missing comma between y and z. In earlier version this would pass.
-Anders


"rajani" <rajani@discussions.microsoft.com> wrote in message
news:C71465F5-F7E8-4AE0-9F8C-EC98233C650F@microsoft.com...
> Yes,Anders
> That's what we normally do.
>
> Guess what finally we nailed out the problem.
> One of our sub folders causing this.
> First we renamed the folder(just to exclude files in them from build) and
> build went thru fine.
> next we renamed back it to original folder name and copied all its
contents
> (i mean prg,scx etc.,) one after the one and doing build in between.
> finally finally we found the prg that causing the error.
> If we just exclude that single prg then build is fine.
>
> Interestingly ,we deleted the whole code in that prg but still get error
> when we do build !!
> Actually there r no syntax errors or anything like that in that prg.we've
> been using it for years.
> Any ideas what's happening there.
> As u know it definetly not with the code in that prg as we blanked out
> completely but still get error!!
> Thanks
>
> "Anders Altberg" wrote:
>
> >
> > "rajani" <rajani@discussions.microsoft.com> wrote in message
> > news:E957E0A7-0CF0-4924-8167-ACC059468DA5@microsoft.com...
> > > Hi Rick
> > > That's what we do.we dont have permanent project file.Everytime we
> > recreate
> > > project file while doing build.
> > >
> >
> > Do you start with a completely new project file to which yiyu have only
> > added the startup Main file? VFP will then add files to the project as
they
> > are referenced on the code.
> >
> > -Anders
> >
> >

Paul
Tue Nov 30 20:43:15 CST 2004

There might be some weird invisible character in that file. I've seen things
like that happen. Throw it away and paste just the text from it into a new
file. Even use WordPad if necessary.



"rajani" <rajani@discussions.microsoft.com> wrote in message
news:C71465F5-F7E8-4AE0-9F8C-EC98233C650F@microsoft.com...
> Yes,Anders
> That's what we normally do.
>
> Guess what finally we nailed out the problem.
> One of our sub folders causing this.
> First we renamed the folder(just to exclude files in them from build) and
> build went thru fine.
> next we renamed back it to original folder name and copied all its
> contents
> (i mean prg,scx etc.,) one after the one and doing build in between.
> finally finally we found the prg that causing the error.
> If we just exclude that single prg then build is fine.
>
> Interestingly ,we deleted the whole code in that prg but still get error
> when we do build !!
> Actually there r no syntax errors or anything like that in that prg.we've
> been using it for years.
> Any ideas what's happening there.
> As u know it definetly not with the code in that prg as we blanked out
> completely but still get error!!
> Thanks
>
> "Anders Altberg" wrote:
>
>>
>> "rajani" <rajani@discussions.microsoft.com> wrote in message
>> news:E957E0A7-0CF0-4924-8167-ACC059468DA5@microsoft.com...
>> > Hi Rick
>> > That's what we do.we dont have permanent project file.Everytime we
>> recreate
>> > project file while doing build.
>> >
>>
>> Do you start with a completely new project file to which yiyu have only
>> added the startup Main file? VFP will then add files to the project as
>> they
>> are referenced on the code.
>>
>> -Anders
>>
>>

Sietse
Wed Dec 01 01:47:26 CST 2004

Hi Rijani,
Maybe the FXP is readonly and cannot be overwritten?

HTH,
Sietse Wijnker

"rajani" <rajani@discussions.microsoft.com> wrote in message
news:C71465F5-F7E8-4AE0-9F8C-EC98233C650F@microsoft.com...
> Yes,Anders
> That's what we normally do.
>
> Guess what finally we nailed out the problem.
> One of our sub folders causing this.
> First we renamed the folder(just to exclude files in them from build) and
> build went thru fine.
> next we renamed back it to original folder name and copied all its
> contents
> (i mean prg,scx etc.,) one after the one and doing build in between.
> finally finally we found the prg that causing the error.
> If we just exclude that single prg then build is fine.
>
> Interestingly ,we deleted the whole code in that prg but still get error
> when we do build !!
> Actually there r no syntax errors or anything like that in that prg.we've
> been using it for years.
> Any ideas what's happening there.
> As u know it definetly not with the code in that prg as we blanked out
> completely but still get error!!
> Thanks
>
<rest snipped>

Dan
Wed Dec 01 12:07:53 CST 2004

You told the whole story in great detail but left out the name of the
offending file.

rajani wrote:
> Yes,Anders
> That's what we normally do.
>
> Guess what finally we nailed out the problem.
> One of our sub folders causing this.
> First we renamed the folder(just to exclude files in them from build)
> and build went thru fine.
> next we renamed back it to original folder name and copied all its
> contents (i mean prg,scx etc.,) one after the one and doing build in
> between. finally finally we found the prg that causing the error.
> If we just exclude that single prg then build is fine.
>
> Interestingly ,we deleted the whole code in that prg but still get
> error when we do build !!
> Actually there r no syntax errors or anything like that in that
> prg.we've been using it for years.
> Any ideas what's happening there.
> As u know it definetly not with the code in that prg as we blanked out
> completely but still get error!!
> Thanks
>
> "Anders Altberg" wrote:
>
>>
>> "rajani" <rajani@discussions.microsoft.com> wrote in message
>> news:E957E0A7-0CF0-4924-8167-ACC059468DA5@microsoft.com...
>>> Hi Rick
>>> That's what we do.we dont have permanent project file.Everytime we
>>> recreate project file while doing build.
>>>
>>
>> Do you start with a completely new project file to which yiyu have
>> only added the startup Main file? VFP will then add files to the
>> project as they are referenced on the code.
>>
>> -Anders