Home |
Search |
Today's Posts |
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
conditional compile for LoadPicture?
Have some code that takes a .bmp file and puts the image on a popup menu
item. This uses LoadPicture and CommandBarButton.Picture I thought that this would work in all version of Excel 2000, but it doesn't compile in this version: Excel 2000 9.0.3821 SR-1 Now would it be possible to use conditional compilation so it will compile in 2002 and 2003, but not in 2000? I would then just use a FaceID for 2000. I had a good search for this, but couldn't find any clear guidance and my impression is that this can't be done. The trouble is I need to differentiate 2000 and above 2000. I understand 97 and above 97 would be less trouble as there is the VBA6 constant. Thanks for any advice on this. RBS |
#2
Posted to microsoft.public.excel.programming
|
|||
|
|||
conditional compile for LoadPicture?
the only compile constant differentiates VBA6 from VBA5 (xl97 from later
versions). The usual recomendation is to put it in a separate procedure and which is called based on the version number. Then don't compile the code and if the function is never accessed, it will never get compiled. -- Regards. Tom Ogilvy "RB Smissaert" wrote: Have some code that takes a .bmp file and puts the image on a popup menu item. This uses LoadPicture and CommandBarButton.Picture I thought that this would work in all version of Excel 2000, but it doesn't compile in this version: Excel 2000 9.0.3821 SR-1 Now would it be possible to use conditional compilation so it will compile in 2002 and 2003, but not in 2000? I would then just use a FaceID for 2000. I had a good search for this, but couldn't find any clear guidance and my impression is that this can't be done. The trouble is I need to differentiate 2000 and above 2000. I understand 97 and above 97 would be less trouble as there is the VBA6 constant. Thanks for any advice on this. RBS |
#3
Posted to microsoft.public.excel.programming
|
|||
|
|||
conditional compile for LoadPicture?
Thanks, will try that, although it is not great not being able to
compile. I suppose I could temporarily comment out those bits, compile and then put them back. Maybe not worth the trouble and better stick with a simple FaceID. RBS Tom Ogilvy wrote: the only compile constant differentiates VBA6 from VBA5 (xl97 from later versions). The usual recomendation is to put it in a separate procedure and which is called based on the version number. Then don't compile the code and if the function is never accessed, it will never get compiled. -- Regards. Tom Ogilvy "RB Smissaert" wrote: Have some code that takes a .bmp file and puts the image on a popup menu item. This uses LoadPicture and CommandBarButton.Picture I thought that this would work in all version of Excel 2000, but it doesn't compile in this version: Excel 2000 9.0.3821 SR-1 Now would it be possible to use conditional compilation so it will compile in 2002 and 2003, but not in 2000? I would then just use a FaceID for 2000. I had a good search for this, but couldn't find any clear guidance and my impression is that this can't be done. The trouble is I need to differentiate 2000 and above 2000. I understand 97 and above 97 would be less trouble as there is the VBA6 constant. Thanks for any advice on this. RBS |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Forum | |||
compile | New Users to Excel | |||
Won't Compile | Excel Discussion (Misc queries) | |||
VBAProject name compile error, not defined at compile time | Excel Programming | |||
LoadPicture - how to keep .jpg compression | Excel Programming | |||
LoadPicture Pathname or no Pathname | Excel Programming |