I have been occasionally suffering from program failures. I get a box that states that the program has performed an illegal operation. What can I do to avoid this? It is quite inconvenient. Thank you.
NATE
NATE
-
-
RE: illegal error
Nate, these are complex systems and errors can crop up in lots of places, caused by many different things. No meaningful response to your question can be made, I fear, without many more details from you.
Try describing the context in which the error occurs. What are you asking Alpha Five to do at the moment of the error? What is the exact error message that you receive? Does the error happen the same way each time? Can you describe the keystrokes or mouseclicks leading to the error?
-- tom -
RE: illegal error
OK here we go:
I'm in the design of a report that I'm working on. I'm trying to get the "Conditional Objects Properties" to have two statements for the "Odd" and "Even" labels:
Var->Prevrec=0 Odd
Var->Prevrec=1 Even
The idea here is that when Prevrec =1 or 0 that the "Odd" or "Even" condition occurs. I'm just trying to get the background to change colors. (I've used a sample method that was supplied to me and the background works on everyother 5 lines. You may be familiar with this sample)
Now, what I have done, is that I went to the detail section on the report and right clicked; this brings up the option of "actions." I clicked on "actions" and wrote the following code into the "OnRecord" option (the only one available)for the "Detail" section.
tbl = table.current()
tbl.fetch_first()
DIM Prevrec AS N
prev=tbl.Action_By
WHILE .NOT. tbl.fetch_EOF()
tbl.fetch_next()
new=tbl.Action_By
IF newprev
IF Prevrec=0
Prevrec=1
ELSE Prevrec=0
END IF
END IF
prev=new
END WHILE
I'm simply trying to get the Global variable Prevrec to be either a 1 or 0 if the firstfield (Action_By)in the current record is not the same as the firstfield in the previous record. This will allow me, hopefully, to change backgrounds everytime the contents of the firstfield changes as the program goes through all the records in the table.
Mind you. I have learned this programming by the seat of my pants, and I need some constructive criticism and help:-)
What am I doing wrong? Am I close? Thanks Tom.
NATE
Comment
-
RE: illegal error
Here is the actual code I'm getting when the program shuts down:ALPHA5 caused an invalid page fault in
module SH31W32.DLL at 017f:0a931dd8.
Registers:
EAX=7466654c CS=017f EIP=0a931dd8 EFLGS=00010202
EBX=020a2f00 SS=0187 ESP=00d83c0c EBP=00d83c60
ECX=00000001 DS=0187 ESI=00ff0000 FS=46df
EDX=7466654c ES=0187 EDI=00ff0080 GS=0000
Bytes at CS:EIP:
8b 0a 25 00 00 ff ff 89 0f 66 ff 40 0c f6 44 24
Stack dump:
00d83c60 01949eb5 00ff0000 020a2f00 bff7b9ae 00000001 00000001 0a931d46 00000005 01949eb5 01949eb0 005e6241 00ff0000 00000005 00000001 005e62e7Comment
-
RE: illegal error
I don't think it's permitted to manipulate the record pointer for the current table, in the middle of a report. Once the record pointer is moved by your code, how does Alpha Five know how to put it back where it belongs? i.e. which record prints next?
I've sent you an email message, so look for it in your inbox.
-- tomComment
-
RE: illegal error / MAJOR PROBS
Thanks Tom,
I changed the coding so that the computer wouldn't run every file over and over again. However, I'll get with you on that shortly.
I HAVE A HUGE PROBLEM. The report I was working on earlier no longer exists because I thought it was causing my computer to crash the Alpha software. However, that wasn't the case. Everytime that I try to work in the report section the software crashes a couple minutes later. I'm not even trying to run the scripts. I'm just in the design mode trying to recreate the layout. I have rebooted my computer several times; went as far as shutting it off. I have reinstalled the Alpha software; I updated my virus scan, just incase, and found no viruses when I ran the program. I keep getting the following two messages when windows tells me that an operation error had occurred and the program is going to be closed:
ALPHA5 caused a stack fault in module A2CNTRL.DLL at 017f:00acbcfe.
Registers:
EAX=00000000 CS=017f EIP=00acbcfe EFLGS=00010206
EBX=00000000 SS=0187 ESP=00c91ce8 EBP=00c9214c
ECX=0208022c DS=0187 ESI=00000000 FS=4b9f
EDX=02092bf0 ES=0187 EDI=00c9259a GS=0000
Bytes at CS:EIP:
53 8d 45 f4 56 33 db 66 89 5d fe 57 50 89 5d d0
Stack dump:
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
and the second detail messages is:
ALPHA5 caused an invalid page fault in
module MFC40.DLL at 017f:7b9812b6.
Registers:
EAX=000000b9 CS=017f EIP=7b9812b6 EFLGS=00010203
EBX=00000001 SS=0187 ESP=01acfbbc EBP=01acfc08
ECX=00000000 DS=0187 ESI=00000b98 FS=3a97
EDX=00000000 ES=0187 EDI=01d57304 GS=2d6e
Bytes at CS:EIP:
f7 71 08 8b 44 24 0c 89 10 8b 41 04 85 c0 74 12
Stack dump:
01d572e4 7b9812ef 00000b98 01acfbcc ffffffff 7b9848a8 00000b98 01acfbe8 00c60288 00000000 00000001 bff74a5c 7b9ac034 7ba46b10 00c601b8 00c601b8
Does this stuff mean anything to you? Is my computer to blame?
NATE
Comment
-
RE: illegal error / MAJOR PROBS
Yes, those are terrible messages to see. There are several things to try. If I were in your shoes I would:
1) Make backup copies of all DBF and FPT files. This is where your actual data is stored. ( In fact, I recommend *two* backup copies, in separate folders or on diskette, zip disk, or tape. )
2) I'd reboot my pc and run scandisk to correct any lingering disk errors.
3) I'd open Alpha Five, and then open the database. From the control panel I'd select File and then Database Compact, and let Alpha Five compact the database. If some of your tables will not compact, note their names, these are likely involved in your difficulties. If this happens, I'd use Alpha Five to actually delete the tables which could not be compacted. Once deleted, I'd compact the remaining tables using Database Compact. Then, I'd close Alpha Five and using Windows Explorer I'd copy the backup copies of the DBF and FPT files back to the database folder. Then I'd open Alpha Five and 'add' these tables to the database. Finally, I'd compact the database again. Eventually you should be able to compact all tables in the database without any being rejected.
4) Only then would I try designing new reports. If I hit more trouble of the kind you describe I would guess it's something in my field rules... I would work through the tables one at a time, removing the field rules, one at a time, until everything works.
These are complex systems and there are lots of things that can go wrong, but perhaps this will give you some direction.
-- tomComment
-
RE: illegal error
Red,
This is just an off chance because I noticed that you are mentioned colors.
I eliminated a crash problem that I narrowed down to color equations on embedded browses. But only on certain computers. I did away with the color equations and since then no crashes.
Could this be your problem
MichaelComment
-
RE: illegal error
Seeing the MFC40DLL mentioned in one of the errors causes me to ask:
Did you install any new programs recently? It's possible that one of them installed an outdated version of one of the system files which are mentioned in the errors.
Check the dates of the MFC*.dll and MFC40*.dll files in the system32 folder and compare them with the versions in the A5 program folder. Also check the install.log in the A5 program folder to see if they were installed. Old versions of these files used to casue horrendous problems which went away once up to date versons were copied into the system32 folder.
FinianFinian
Comment
Comment