![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I am developing in Filemaker 5.5. How difficult is it to upgrade to Filemaker pro 8 advanced? I only have 15 tables and was able to convert them but have not had a chance to actually run the scripts to see if they work correctly. |
|
Will version 8 permit viewing variables and/or modifying them from within a script? |
#3
| |||
| |||
|
|
Flower Gardener <n... (AT) optonline (DOT) net> wrote: I am developing in Filemaker 5.5. How difficult is it to upgrade to Filemaker pro 8 advanced? I only have 15 tables and was able to convert them but have not had a chance to actually run the scripts to see if they work correctly. If you work very neatly, you can upgrade the files. But then you have your 5.5 solution running on 8, which is slower. If you'r going to FM8, you better redesign the solution, using the new FMP 7/8 tools, and transfer the data. Will version 8 permit viewing variables and/or modifying them from within a script? You can put a variable in a calculation and thus show it in a dialog box. However, if you want to see it on a layout or need to user to put in or change value, you still need a field. --http://clk.ch |
#4
| |||
| |||
|
|
Flower Gardener <ngeti (AT) optonline (DOT) net> wrote: I am developing in Filemaker 5.5. How difficult is it to upgrade to Filemaker pro 8 advanced? I only have 15 tables and was able to convert them but have not had a chance to actually run the scripts to see if they work correctly. If you work very neatly, you can upgrade the files. But then you have your 5.5 solution running on 8, which is slower. If you'r going to FM8, you better redesign the solution, using the new FMP 7/8 tools, and transfer the data. What do you mean by redesigning the solution? Do you mean rewrite the |
#5
| |||
| |||
|
|
If you work very neatly, you can upgrade the files. But then you have your 5.5 solution running on 8, which is slower. |
#6
| |||
| |||
|
|
I'm a little surprised at this redesign advice. By the way, by redesign, they mean that you should rethink all of your tables, fields, relationships and scripts and rebuild them all from scratch. I spent about 3 months getting my solution translated (it had 80 files) and although it was somewhat hellish and I'm still cleaning up some of the 8.0 issues, I couldn't imagine recreating the whole thing from scratch. I would also think very carefully about combining all of your files into one, which 8 now allows. If you do that, all of you layouts will be in one large list. All of your scripts will also be in a gigantic list. I actually prefer to keep separate parts of the system in separate files, although I am sure I will consolidate some of my files over time. You can learn the new stuff when you add new features, there's plenty of time for that. Hey Christoph- I noticed you said this: If you work very neatly, you can upgrade the files. But then you have your 5.5 solution running on 8, which is slower. What exactly is slower? |
#7
| |||
| |||
|
|
If you work very neatly, you can upgrade the files. But then you have your 5.5 solution running on 8, which is slower. If you'r going to FM8, you better redesign the solution, using the new FMP 7/8 tools, and transfer the data. What do you mean by redesigning the solution? Do you mean rewrite the scripts using FM8 language or something more complex? |
#8
| |||
| |||
|
|
You suggestions make a lot of sense to me. I agree that putting everything in one table would be a nightmare. What would happen if there was a crash of some kind and a single record got corrupted. How could anyone sort out the mess? This is a major problem with Microsoft Access including leading to poor performance. My application appears quite difficult and took the former programmer a year or more to finish. All I want to do is add some minor fixes; not rewrite the entire application. |
![]() |
| Thread Tools | |
| Display Modes | |
| |