Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


sal88 last won the day on September 25

sal88 had the most liked content!

Community Reputation

1 Neutral

About sal88

  • Rank

Profile Information

  • Gender
  • Location
    United Kingdom

FileMaker Experience

  • Skill Level
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
  • OS Version
  1. Brilliant! that works. thank you very much Olger!
  2. Hi all My scheduled server scripts call up my onwindowopen startup script, which is great. I specify that the startup script exits if it is being run from the server. The actual scheduled script then runs fine. However I don't want any of my scheduled scripts to run if the plugins are not enabled on the server. I thought I could achieve this by utilising the 'halt' script step on the startup script in the event that the plugins were found not to be enabled. While it does halt the startup script, it does not also halt the script that called it up (the scheduled script). I'm guessing though that this is because the scheduled script has not actually 'called' the startup script. Should it work the way I expected? Or is there a way to disable the running of scheduled scripts without having to specify in each individual one that they should not run if there is no plugin. MT
  3. Execute SQL - Insert and Select

    I'm still stuck on this - I can't work out if ESS is even meant for my purposes. Any help whatsoever would be much appreciated. Many thanks
  4. Hi all I'm trying to export my filemaker records to my external sql database via the execute sql script step but am getting a number of errors. I can see my external ODBC source and can generally write to it (I can go to the respective layout and click 'new record'). My query basically as follows: "INSERT INTO dbo.Log ( dbo.Log.log_id, dbo.Log.log_case_idf, dbo.Log.Labour_TOTALS_Labour_Cost, dbo.Log.Labour_TOTALS_Item_Sale) SELECT Log_Log.log_id, Log_Log.log_case_idf, Log_Log.Labour_TOTALS_Labour_Cost, Log_Log.Labour_TOTALS_Item_Sale, FROM Log WHERE Log_Log.Log_Type = '2'" My first question is: is it even possible to export to an odbc source with a 'insert INTO SELECT' query? Many thanks
  5. Can't see DSN

    No i just ticked the Enable ODBC/JDBC checkbox on the server. I tried to add the DSN from my client machine. The DSN is on my local machine.....Aaaaand I've just set up the DSN on the server instead and I can now see it! I take it this is the correct and only way for it to work for a hosted database?
  6. Can't see DSN

    I can see the DSNs in a newly created local blank database. However when i upload this to our server the DSNs no longer appear. I've enabled ODBC in filemaker server but no joy.
  7. Can't see DSN

    I'm still nowhere further on this. Is there a (very simple) guide somewhere for setting up ODBC? Thanks
  8. Can't see DSN

    My FileMaker client is 64-bit. So i deleted the ODBC 32-bit DSN and added it to the 64-bit version instead. But it is still not showing in the external data source list.
  9. Can't see DSN

    Hi all I'm trying to connect to an Azure SQL database from FileMaker 16. I've added the DSN via ODBC 32bit (see pic). However, when I go to File>Manage>External Data Sources, it doesn't show the DSN. Where am I going wrong? Thanks in advance
  10. Thanks Fitch, I'll give it a go. Loving the importing option though so might just go for that!
  11. Would they be able to have full access to data in the host file but limited in the reports file? To clarify: Main database - users have full access to data (restricted only by layout features) but cannot edit scripts/layouts/database Reports database - full access to design privileges, and access to data in main database but on a read only basis I've tried to define the privileges in the host file but it doesn't appear to work, i'm guessing there's a conflict in defining privileges in the host file for files that reference it but NOT for users that are accessing the host file directly (in the usual manner). Using external authentication might be complicating things also, perhaps when I am linking to the host file from the reports file it doesn't ask for authentication? Is native filemaker authentication better for this type of thing? Thanks
  12. Hi all Users are more frequently than ever requesting that custom reports be made. Up till now this has involved me creating layouts and scripts that can produce the data/reports in the form they want. I'm wondering if now it might be possible to let them take control of reporting in a way that is separate from the current database (which is heavy on GUI and disabling of features for ordinary users). I'm thinking of creating a totally new database which users would be able to completely edit from a design perspective, which would point to the main database as an external data source. However I would like it so that they would NOT be able to edit/create/delete those external records. I've had a play with it and can't seem to get it to work (we're using external authentication via windows server active directory). Is such a thing possible? Many thanks
  13. Brilliant. The number of users accessing such records is very low (if not 1), even if privileges are in place, so I'll leave it as it is for the moment. Cheers!
  14. Thanks Fitch. One more thing I've wondered about is why, in the case of performing multiple set fields (upon the same instance, e.g. lines 54-58), you don't need to set the $error variable after each set field, is it not possible that line 54 could produce an error but not line 58 (in which case it would not record the error).
  15. Thanks Fitch. I take it the below is OK then for adding stock? I think I'm unsure about (and I'm really splitting hairs here) is whether I should apply line 54 at the beginning, followed by 55-58, then change the stock levels but based on the 'recurring_services_stock' relationship and not the 'recurring_services_preview' relationship. The latter being based on the recurring_services::RS_Temp_Stock_IDF field.

Important Information

By using this site, you agree to our Terms of Use.