![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have developed a FileMaker "front end" to an Oracle database via ODBC that allows me to query for info and also to UPDATE. It works fine. Everyone else in our workgroup has to use the Oracle interface...which is far, far worse than anything on the interface hall of shame. With a little tweaking, everyone in our work group could use my Filemaker solution. However, there are a few issues. The administrators are nervous about security issues when doing UDPATEs since some of the security is built into the Oracle user interface, itself, and that would have to be duplicated in the FileMaker version. |
#3
| |||
| |||
|
| By the way, it seems that there is no "try before you buy" download for FileMaker Server Advanced. Is that correct? |
#4
| |||
| |||
|
|
William Maslin wrote: By the way, it seems that there is no "try before you buy" download for FileMaker Server Advanced. Is that correct? Technet membership (c.$150 p.a) comes with a free FMSA license for dev/testing (limited 5 concurrent user) |
#5
| |||
| |||
|
|
William Maslin wrote: I have developed a FileMaker "front end" to an Oracle database via ODBC that allows me to query for info and also to UPDATE. It works fine. Everyone else in our workgroup has to use the Oracle interface...which is far, far worse than anything on the interface hall of shame. With a little tweaking, everyone in our work group could use my Filemaker solution. However, there are a few issues. The administrators are nervous about security issues when doing UDPATEs since some of the security is built into the Oracle user interface, itself, and that would have to be duplicated in the FileMaker version. You don't need FM Server Advanced, just the regular version. Set up your DSN on the FM server machine and point to that DSN when setting up the external data sources in FileMaker. You will set the user name and password in the external data sources (ESS) setup, so that is the only place you need to change it each month. The DSN does not need to be set up for each user since it has been set up on the FM server, and the password therefore does not need to be changed for each user. If the Oracle DBA is concerned about security, then they need to make available to you an account that only has the privileges your users should have. |
#6
| |||
| |||
|
|
In article <hdkg8n$pcj$1 (AT) news (DOT) motzarella.org>, Howard Schlossberg <howard (AT) nospam (DOT) fmprosolutions.com> wrote: You don't need FM Server Advanced, just the regular version. Set up your DSN on the FM server machine and point to that DSN when setting up the external data sources in FileMaker. You will set the user name and password in the external data sources (ESS) setup, so that is the only place you need to change it each month. The DSN does not need to be set up for each user since it has been set up on the FM server, and the password therefore does not need to be changed for each user. If the Oracle DBA is concerned about security, then they need to make available to you an account that only has the privileges your users should have. Thanks for the info! At the moment, everything in my solution (FMP 9) works with "stored" procedures, ie, the username and password are stored in the Import scripts and Send SQL stuff. I played with ESS briefly and it works great for single tables, but even trying a FIND using just two find criteria (one each in two related Oracle tables) was unacceptable slow. In the future I might try the View route, but not yet. |
#7
| |||
| |||
|
|
William Maslin wrote: In article <hdkg8n$pcj$1 (AT) news (DOT) motzarella.org>, Howard Schlossberg <howard (AT) nospam (DOT) fmprosolutions.com> wrote: You don't need FM Server Advanced, just the regular version. Set up your DSN on the FM server machine and point to that DSN when setting up the external data sources in FileMaker. You will set the user name and password in the external data sources (ESS) setup, so that is the only place you need to change it each month. The DSN does not need to be set up for each user since it has been set up on the FM server, and the password therefore does not need to be changed for each user. If the Oracle DBA is concerned about security, then they need to make available to you an account that only has the privileges your users should have. Thanks for the info! At the moment, everything in my solution (FMP 9) works with "stored" procedures, ie, the username and password are stored in the Import scripts and Send SQL stuff. I played with ESS briefly and it works great for single tables, but even trying a FIND using just two find criteria (one each in two related Oracle tables) was unacceptable slow. In the future I might try the View route, but not yet. Are you sure all those fields you are searching on, as well as all fields on which you are basing relationships, were indexed in the SQL db? Remember that FM is not providing the indexes on those since the data lives in SQL. |
![]() |
| Thread Tools | |
| Display Modes | |
| |