Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
How serious are really SP2 Reporting bugs
Message
From
06/03/2008 09:20:04
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Germany
 
 
To
06/03/2008 08:39:24
Jay Johengen
Altamahaw-Ossipee, North Carolina, United States
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Environment versions
Visual FoxPro:
VFP 9 SP2
Miscellaneous
Thread ID:
01299233
Message ID:
01299282
Views:
11
All what I use in VFP9 SP1, except the report apps.
Anyway, some apps are available in VFP7-9 and use ANCHOR ICASE TRY CATCH EVL etc.
Lot of work is done via compile switches.

Think on something like
*h file
#IF VERSION(5)<800 THEN
 #DEFINE dnVersion7_Prog			'YES'	&& Ist älter als Version  8.00
#ENDIF &&VERSION(5)<800
#IF VERSION(5)<900 THEN
 #DEFINE dnVersion8_Prog			'YES'	&& Ist älter als Version  9.00
#ENDIF &&VERSION(5)<900
#IF VERSION(5)<1000 THEN
 #DEFINE dnVersion9_Prog			'YES'	&& Ist älter als Version 10.00
 #IF RIGHT(VERSION(4),4)='5815' THEN
*SP2
  #DEFINE dcV9SP				'5815'
 #ELSE &&RIGHT(VERSION(4),4)='5815'
  #IF RIGHT(VERSION(4),4)='3504' THEN
   #DEFINE dcV9SP				'3504'
  #ELSE &&RIGHT(VERSION(4),4)='3504'
*VFP9 vanilla
   #DEFINE dcV9SP				'2412'
  #ENDIF &&RIGHT(VERSION(4),4)='3504'
 #ENDIF &&RIGHT(VERSION(4),4)='5815'
#ENDIF &&VERSION(5)<1000

*prg
#IFDEF dnVersion7_Prog THEN
*Only if version lower the VFP 8
 #DEFINE REMOVEPROPERTY				*
 #DEFINE DOEVENTS				DOEVENTS()

PROCEDURE EVL
 LPARAMETERS;
   tv1,tv2
 RETURN IIF(EMPTY(tv1)tv2,tv1)
ENDPROC &&EVL
#ENDIF &&dnVersion7_Prog

#IFNDEF dnVersion7_Prog THEN
TRY
blabla
catch
endtry
#ELSE &&dnVersion7_Prog
on error
blabla
#ENDIF &&dnVersion7_Prog
There is a stack of h files, and somewhere in it's top those constants are defined. All what I need is to compile with the target version.

for example my startup looks like
#IFDEF dnVersion7_Prog THEN
 IF VERSION(5)>799 THEN
  MESSAGEBOX('Falsche Version',MB_IconInformation)
  RETURN False
 ENDIF &&VERSION(5)>799
#ELSE &&dnVersion7_Prog
 #IFDEF dnVersion8_Prog THEN
  IF !BETWEEN(VERSION(5),800,899) THEN
   MESSAGEBOX('Falsche Version',MB_IconInformation)
   RETURN False
  ENDIF &&!BETWEEN(VERSION(5),800,899)
 #ELSE &&dnVersion8_Prog
  #IFDEF dnVersion9_Prog THEN
   IF !BETWEEN(VERSION(5),900,999) THEN
    MESSAGEBOX('Falsche Version',MB_IconInformation)
    RETURN False
   ENDIF &&!BETWEEN(VERSION(5),900,999)
   IF !RIGHT(VERSION(4),4)==dcV9SP THEN
    MESSAGEBOX('Falsches Servicepack',MB_IconInformation)
    RETURN False
   ENDIF &&!RIGHT(VERSION(4),4)==dcV9SP
  #ENDIF &&dnVersion9_Prog
 #ENDIF &&dnVersion8_Prog
#ENDIF &&dnVersion7_Prog
<pre>
>How do you develop in SP2 but distribute in SP1? What if you develop something that is not available in SP1?
>
>>SP2 broke data group headers repeated on subsequent pages bug stopps me from using SP2 I use it for development but distribution will be on SP1 with the reportapps from SP2 compiled under SP1.
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord

Weeks of programming can save you hours of planning.

Off

There is no place like [::1]
Previous
Reply
Map
View

Click here to load this message in the networking platform