![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
"Variables are not supported in file paths that are stored in container fields" |
#3
| |||
| |||
|
|
Michael Paine wrote on (11/5/2005): "Variables are not supported in file paths that are stored in container fields" If that's saying what I think it's saying, I would have to say, "That sucks." I routinely use a calculated path to an image (including field values as variables) returned as a container to display the image (this in FM7). Are you telling me they took that capability away? That would contradict the oft-expressed assertion that FM8 files are fully functional in FM7 except for FM8-specific features. Matt |
#4
| |||
| |||
|
|
The calculated conatiners containing references to images do still work as expected. And these calculations still contain references to fields. And the contaents of these fields differ from record to record. Thus the next calc does have an image as result: "image:./images/" & ArtistID & "_01.jpg" Ursus "Matt Wills" <I'm (AT) Witz (DOT) end> schreef in bericht news:Va9bf.133$w_6.10 (AT) trndny09 (DOT) .. Michael Paine wrote on (11/5/2005): "Variables are not supported in file paths that are stored in container fields" If that's saying what I think it's saying, I would have to say, "That sucks." I routinely use a calculated path to an image (including field values as variables) returned as a container to display the image (this in FM7). Are you telling me they took that capability away? That would contradict the oft-expressed assertion that FM8 files are fully functional in FM7 except for FM8-specific features. Matt |
#5
| |||
| |||
|
|
OK, then, I guess I completely misunderstood what Michael was saying. Whew. I was worried I would have to redesign this thing when I upgraded it to 8. Michael, can you elaborate? Matt ursus.kirk wrote on (11/5/2005): The calculated conatiners containing references to images do still work as expected. And these calculations still contain references to fields. And the contaents of these fields differ from record to record. Thus the next calc does have an image as result: "image:./images/" & ArtistID & "_01.jpg" Ursus "Matt Wills" <I'm (AT) Witz (DOT) end> schreef in bericht news:Va9bf.133$w_6.10 (AT) trndny09 (DOT) .. Michael Paine wrote on (11/5/2005): "Variables are not supported in file paths that are stored in container fields" If that's saying what I think it's saying, I would have to say, "That sucks." I routinely use a calculated path to an image (including field values as variables) returned as a container to display the image (this in FM7). Are you telling me they took that capability away? That would contradict the oft-expressed assertion that FM8 files are fully functional in FM7 except for FM8-specific features. Matt |
#6
| |||
| |||
|
|
As noted previously, I am working on a layout/script that will populate container fields with coloured pictures that depend on other fields in the table. I was hoping to do this by using the Insert Picture script step and assign a variable to the image file path and name (eg "image:/pics/" & table icname ). However I couldn't get this to work. Ieventually found the following reference in FM8 help: "Variables are not supported in file paths that are stored in container fields" I can work around the problem with a long sequence of IF ELSE statements but it would have been much simpler if variable file paths were supported. Another example would be using script to select an employee picture using employee number (to avoid users having to manually select from folder listings). Any suggestions for a workaround? |
icname, and then use that variable in the 'filename' for the
#7
| |||
| |||
|
|
The script below did not work as I expected (one problem may be that the global variable $$pic is not recognised within the insert picture statement (it automatically puts quotes around it). When I checked Help it came up with the limitation I mentioned before Enter Browse Mode Go to Layout [ “fancy_test” (Vehicles) ] Set Variable [ $$pic; Value:"image ics/" & Vehicles::head_drv_colour ]Go to Field [ Vehicles::head_drv_pic ] Insert Picture [ “$$pic” ] [ Reference ] |
#8
| |||
| |||
|
|
Michael Paine wrote: The script below did not work as I expected (one problem may be that the global variable $$pic is not recognised within the insert picture statement (it automatically puts quotes around it). When I checked Help it came up with the limitation I mentioned before Enter Browse Mode Go to Layout [ “fancy_test” (Vehicles) ] Set Variable [ $$pic; Value:"image ics/" & Vehicles::head_drv_colour ]Go to Field [ Vehicles::head_drv_pic ] Insert Picture [ “$$pic” ] [ Reference ] I just tried the equivalent of this and it worked: Set Variable [ $$pic; Value:"image:/pics/" & Vehicles::head_drv_colour ] Go to Field [ Vehicles::head_drv_pic ] Insert Picture [ “$$pic” ] Note the extra slash after image: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Howard Schlossberg (818) 883-2846 FM Pro Solutions Los Angeles, California FileMaker 7 Certified Developer Associate Member, FileMaker Solutions Alliance |
#9
| |||
| |||
|
|
The script below did not work as I expected (one problem may be that the global variable $$pic is not recognised within the insert picture statement (it automatically puts quotes around it). When I checked Help it came up with the limitation I mentioned before Enter Browse Mode Go to Layout [ “fancy_test” (Vehicles) ] Set Variable [ $$pic; Value:"image ics/" & Vehicles::head_drv_colour ]Go to Field [ Vehicles::head_drv_pic ] Insert Picture [ “$$pic” ] [ Reference ] I will try Insert Picture [ "image ics/" & Vehicles::head_drv_colour ]However, my logic would be greatly simplified if I could use a global variable in the script. Michael Paine Matt Wills wrote: OK, then, I guess I completely misunderstood what Michael was saying. Whew. I was worried I would have to redesign this thing when I upgraded it to 8. Michael, can you elaborate? Matt ursus.kirk wrote on (11/5/2005): The calculated conatiners containing references to images do still work as expected. And these calculations still contain references to fields. And the contaents of these fields differ from record to record. Thus the next calc does have an image as result: "image:./images/" & ArtistID & "_01.jpg" Ursus "Matt Wills" <I'm (AT) Witz (DOT) end> schreef in bericht news:Va9bf.133$w_6.10 (AT) trndny09 (DOT) .. Michael Paine wrote on (11/5/2005): "Variables are not supported in file paths that are stored in container fields" If that's saying what I think it's saying, I would have to say, "That sucks." I routinely use a calculated path to an image (including field values as variables) returned as a container to display the image (this in FM7). Are you telling me they took that capability away? That would contradict the oft-expressed assertion that FM8 files are fully functional in FM7 except for FM8-specific features. Matt |
#10
| |||
| |||
|
|
Thanks Howard. I will try it again. Maybe the Help text is out of date? Michael Paine Howard Schlossberg wrote: Michael Paine wrote: The script below did not work as I expected (one problem may be that the global variable $$pic is not recognised within the insert picture statement (it automatically puts quotes around it). When I checked Help it came up with the limitation I mentioned before Enter Browse Mode Go to Layout [ “fancy_test” (Vehicles) ] Set Variable [ $$pic; Value:"image ics/" & Vehicles::head_drv_colour ]Go to Field [ Vehicles::head_drv_pic ] Insert Picture [ “$$pic” ] [ Reference ] I just tried the equivalent of this and it worked: Set Variable [ $$pic; Value:"image:/pics/" & Vehicles::head_drv_colour ] Go to Field [ Vehicles::head_drv_pic ] Insert Picture [ “$$pic” ] Note the extra slash after image: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Howard Schlossberg (818) 883-2846 FM Pro Solutions Los Angeles, California FileMaker 7 Certified Developer Associate Member, FileMaker Solutions Alliance |
![]() |
| Thread Tools | |
| Display Modes | |
| |