Stumped_Program_wont_update_Dimensions-Or-DataPage?

[Paul Sarrach]

I am writing a program that for some reason stopped updating the the Dimensionla output. So I put in a Stats to make it go to datapage. It wont. I can call up other programs and it will update. When I try this program nothing it does nothing. 3.5 mr2. Never seen this before, Program is huge do not want to start over. Here is the start up of the program, am I not seeing somehting?.

When I start program it does not ask me if I want to save stats.

PART NAME : 3055_Rooftop
REV NUMBER : 001
SER NUMBER : 001
STATS COUNT : 1

STARTUP =ALIGNMENT/START,RECALL:, LIST= YES
ALIGNMENT/END
MODE/MANUAL
LOADPROBE/2MM
FORMAT/TEXT,OPTIONS,HEADINGS,SYMBOLS, ;NOM,TOL,MEAS,DEV,OUTTOL, ,
CHECK/ 5,1
MOVESPEED/ 60
TIP/T1A0B0, SHANKIJK=0, 0, 1, ANGLE=-179.084
STATS/ON,DATAPAGE,$
DIRECTORY=C:\DATAPAGE\3000,$
DIRECTORY=,$
READ=10,WRITE=20,MEMPAGES=4,DIMENSION NAME,CONTROLCALC OFF,$
STATS/END

[Underspec]

Not sure if you have checked, but it's almost everytime a simple fix to problems like these. Did you check your stats setup? Setups are program specific so if something happened to your program it wouldn't affect the others. Also check to make sure everything is marked as usual

[Paul Sarrach]

Yes, I pulled up an earlier version of this one, copied and pasted the stats into it. It ran and ask if I wanted to save stats?

[Underspec]

Did you double check to make sure there are STATS/ON, STATS/OFF callouts before and after features?

Check the setups of both and see what's different? I'm stumped too now

[Paul Sarrach]

I copied the startup block from that program, and pasted it in the new deleted out the old, and is still jumps right past the stats?

[TRD_racing]

Paul,

I have had this happen to me also. I think back on earlier post It says to deleter your XSTATS11.TMP file. I always rename mine then delete it after I get it working. I don't know why but it worked for me.

[Matthew D. Hoedeman]

I have had problems with the STATS not working correctly before. It started in V3.5 (where else) and I do NOT know if it is still a problem. I can type faster than I can hunt some things down with the mouse, especially since Pcdmis will 'fill-in' once it gets far enough. I had always typed in STAT when I wanted to insert the STATS command, always. It also always worked, until V3.5. Everytime I tried typing in the STATS command, it would not work, so I had to go to the method of hunting it down and inserting it through the menus of Pcdmis, give that a try, see if it fixes your problem.

[TRD_racing]

Paul,

I don't know if this matters but where you have
"DIMENSION NAME" my stats code has "FEATURE NAME"


STATS/ON,DATAPAGE,$
DIRECTORY=C:\DATAPAGE\3000,$
DIRECTORY=,$
READ=10,WRITE=20,MEMPAGES=4,DIMENSION NAME,CONTROLCALC OFF,$
STATS/END

[Paul Sarrach]

No, This has nothing to do with xstat11. It works on everything else. I found and earlier version of this program, and added the stats, and its running. I will have to just add to this program. I just wish I knew what happened to that one, Because I finished it. It ran yesterday, came in today. and, well, we all know about PCDemons. )(*&^$(@*&^@!

[craiger_ny]

.....I can hunt some things down with the mouse, especially since Pcdmis will 'fill-in' once it gets far enough. I had always typed in STAT when I wanted to insert the STATS command, always. It also always worked, until V3.5. Everytime I tried typing in the STATS command, it would not work, so I had to go to the method of hunting it down and inserting it through the menus of Pcdmis, give that a try, see if it fixes your problem.

I have had the same issue with typing in things instead of mousing around for them. I have even had feature data that corrupted on typed in features. It bugs the s#it out of me and I am not sure anyone here will ever locate an explination for it (as if Willcocks/B&S ever would). I'd try what Matt says if in fact you created this by typing in instead of mousing to a menu and doing it. I am not certain that the Xstats11.tmp file is to blame in this case but as a practice you could put this code at the very beginning of your programs that you save the stats with (I sugested this in another thread, it is simple really)

V1 =FILE/EXISTS,C:\PCDMISW\Xstats11.tmp
IF/V1==1
FILE/DELETE,C:\PCDMISW\Xstats11.tmp
END_IF/

Craig

[Underspec]

DIMENSION / FEATURE NAME only tells the stats setup where to begin / capture stats.

Paul do you use the update stats at the end of the program? Or do you use the automatically update stats?

[Paul Sarrach]

Paul,

I don't know if this matters but where you have
"DIMENSION NAME" my stats code has "FEATURE NAME"


STATS/ON,DATAPAGE,$
DIRECTORY=C:\DATAPAGE\3000,$
DIRECTORY=,$
READ=10,WRITE=20,MEMPAGES=4,DIMENSION NAME,CONTROLCALC OFF,$
STATS/END

If you use feature name, it will if I am not mistaken, on give you stats on the feature once. So if you use it in a second alignment, and tolerance it, it will only stats it once in datapage. Some out there, back me or disigree, please do so. My brain hurts.

[Paul Sarrach]

DIMENSION / FEATURE NAME only tells the stats setup where to begin / capture stats.

Paul do you use the update stats at the end of the program? Or do you use the automatically update stats?

auto, it wont even update my dimensions? ? ? ?? ?" shows nothing in the yellow latest dimenional screen? ? ? ? ? ? ?

[Matthew D. Hoedeman]

I use feature name 100% of the time. The main difference between the two options is you can dimension the same feature more than once, and each dimension has a unique ID, but the feature has the same ID. If you dimension the feature more than once, it will ONLY 'save' the LAST data 'assigned' to that feature. For example, you check P001 to ABC and dimension it. You then create an alignment to DEF and dimension P001 again. The data sent to Datapage will be the data for the SECOND dimension (plus anything that was not 'over-written') if you use FEATURE ID. If you use DIMENSION ID, then each dimension will show up in Datapage but not the features and nothing CAN get over-written by a second dimension UNLESS you copy and paste because PCdmis will NOT allow duplicate DIM ID's.

[Paul Sarrach]

Correct, so what I do is call my point say P1, and then my Dim P_1. Then if I use it in somehting else, I can call it say P1_DEF if its to that alignment. And this way my Roadmap is easy to read because the Dimensions and features Look almost the same.