Jump to content

Toni

Members
  • Content count

    83
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Toni

  • Rank
    member
  • Birthday 04/27/1974

Profile Information

  • Gender
    Male
  • Location
    Tirane
  • Interests
    Networking

FileMaker Experience

  • Skill Level
    Intermediate
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
    Windows
  • OS Version
    Windows 7, Windows 10

Recent Profile Visitors

1,895 profile views
  1. Toni

    Printing on dot matrix fx-890 FM16

    Thanks Steve Hopefully I can solve it the way you did. Will come back and let you know with results.
  2. Hello I am having trouble on printing a layout on a dot matrix printer Epson FX-890 with FileMaker16. The database runs on a server. The page is setup in "Letter" format but FileMaker interprets the width smaller than 216mm resulting in starting a new page. In preview mode it shows the truncated page (sth like 140mm x 279mm), if I change the paper format to "Letter fanfold" it shows correctly in Preview but still prints as if the width is 140mm. I tried various drivers for the printer to no successful result. The same layout printed correctly before on FileMaker11 on the same computer, the only difference is that FileMaker11 didn't run from server. Computer runs on Windows7 x86. My guess is it is a problem of how FileMaker interacts with printer drivers. Anyone else has had trouble as described? Any possible solution? Thank you
  3. Hello, I am struggling to make a send event work and I am running out of ideas so a bit of help is needed I have a script which will create a file on the desktop and then email it. After it is created I want the file deleted. Here are the steps of the script which deal with this need: The first one will create the path and filename to be created and then emailed Set Variable [$file; Value: "filewin:"&Get ( DesktopPath )&Substitute( GetAsText ( Get ( CurrentDate ));"/";"")&"_Report.pdf"] The second one will create a variable to be used in cmd as parameter for the del command Set Variable [$filedelete; Value: Replace ( Substitute( $file;"/";"\\");0;9;"")] The last one is the send event step Send Event ["aevt"; "odoc"; "cmd.exe del " &Quote($filedelete)] Unfortunately this will not do the delete, I see the cmd window with path positioned on local desktop which I have moved on disk D ( D:\Desktop>). Using data viewer I can see the value of $filedelete variable is correct, if I copy that value and paste it into cmd window the command will execute correctly. What am I missing? Maybe I need to send the execute command after the line is send (like pressing enter from keyboard if you run the command from cmd)?
  4. I am still on FM11, but as you're asking I am planning in near future to upgrade at 16. Have delayed it because of the not so funny experience when upgrading from FM5 to FM7. Reading documentation about moving from .fp7 to .fmp12 and it sounds smother than from the previous I had at the time.
  5. Thank you both, didn't know these were called audit I had a look at those audit solutions and are very useful so I will definitely give a try on those. I have some sort of things like those already in place. Anyway, I was thinking more on the line on keeping track of the changes to the database made by myself. So I will also try a solution of building a table for this very purpose. I develop for two customers who are in the manufacturer business and they come with every sort of idea every other week so it is becoming increasingly hard to remember why I created one field or one script. The nature of manufacturing is very flexible and changes in lot of aspects, like line of productions, models, etc. so the database has to adapt fast and needs to be tracked. There are even things which are temporary because they are related to a specific product which might be in place for three months for example.
  6. Calendar View File I created this solution because I wanted to have each day as a record. The purpose of it, is assigning working days (business days) an incremental number so that number can be used in other related tables on which is required to calculate working days. It has two main scripts, the firsts populates the year. After year is populated, than holiday days are assigned manually but you can add script at your needs. I left it manually so you can be flexible with it. Where I live is not uncommon to have to work even if it might be a holiday, so every company has different needs. After holidays have been assigned, there is a second script which will define the incremental number of working days. On the holidays this number is equal to the number the nearest next working day has. For example, if 28 and 29 of November are holidays the working day for those will be 282 the same as that on 30 November. This helps in cases someone assigns a job that starts on holiday and calculate the end date of that job. Any idea or contribution to make it better is welcomed. Thank you, Toni Submitter Toni Submitted 02/22/2018 Category Samples FM Version 12  
  7. Toni

    Calendar

    Version 1.0.0

    42 downloads

    I created this solution because I wanted to have each day as a record. The purpose of it, is assigning working days (business days) an incremental number so that number can be used in other related tables on which is required to calculate working days. It has two main scripts, the firsts populates the year. After year is populated, than holiday days are assigned manually but you can add script at your needs. I left it manually so you can be flexible with it. Where I live is not uncommon to have to work even if it might be a holiday, so every company has different needs. After holidays have been assigned, there is a second script which will define the incremental number of working days. On the holidays this number is equal to the number the nearest next working day has. For example, if 28 and 29 of November are holidays the working day for those will be 282 the same as that on 30 November. This helps in cases someone assigns a job that starts on holiday and calculate the end date of that job. Any idea or contribution to make it better is welcomed. Thank you, Toni

    Free

  8. Hello With small to big changes made as often as customer requires and age hitting hard on me , I've come to think about noting somewhere these changes, keeping a log file of them. I think some of you might already have in place such practices. So, what are your best methods in keeping track of what has been done through the years? Thank you, Toni
  9. So you have no problems with that? I do click on one of the fields first, that's a given. Starting to wonder if it is a keyboard related issue or Microsoft Windows
  10. Hello I started working on a new client which has already FileMaker15. I am used with FM11 from years now. One thing I found strange, was the browsing of the fields on manage database window. On FM11 I could easily press on the keyboard the key of starting letter of a field and navigate to the fields with that starting letter, on FM15 it just hangs at the first fields it finds, sometimes jumps from first to second it finds, kind of strange. Let say I want to navigate to a field named "Saturn". On FM11 if I press on keyboard "S" it navigates to the fields starting with "S" every time I press it, I could even press fast enough "sa" and it will navigate on fields starting with "sa". This does not happen on FM15. Is this a known issue, or should I look for some specific option on FM15?
  11. I struggled a bit with the path of BE_FileExist. Thought the path was to be inserted as FileMaker likes it (filewin:/C:/blabla), instead one can insert the path as in Windows (C:\blabla). Very cool option, it works after some testings I did. Thank you once more.
  12. Thanks Olger Never used plugins, time to explore this one. Will let you know
  13. Hello forumers I have a small issue with an export on a network path. Generally the path is alive, but very rarely it can happen that is not reachable. When not reachable, you'll get the error message from FileMaker that file can not be created .... (error code = 800). Since this dialog box can not be suppressed by Error Capture =On, the script will stop there until someone goes and clicks on the OK button of the message. Was wondering, is there a way to check if the path is reachable, and if it is not reachable then to exit script? Thank you, Toni
  14. After some testing, I came with a better way because that Pause/Resume step of script is really annoying. Posting here only the script steps: "Schedule_Time_24h" steps: Install OnTimer Script [] Perform Script [Export_DL4_Call] Set Field [File2::Schedule_Time; 86400] Install OnTimer Script ["Export_DL4_Call"; Interval: File2::Schedule_Time] "Schedule_23_h" steps: Select Window [Current Window] Adjust Window [Hide] Set Field [File2::Schedule_Time; ""] Set Field [File2::Time1; Get ( CurrentTimeStamp )] Set Field [File2::Schedule_Time; Let ( [ hour2 = 23; min2 = 0; sec2 = 0; hour1 = Hour (File2::Time1); min1 = Minute (File2::Time1); sec1 = Seconds (File2::Time1) ]; ( sec2-sec1 ) + ( min2 -min1 )*60 + ( hour2 - hour1)*3600 )] Install OnTimer Script ["Schedule_Time_24h"; Interval: File2::Schedule_Time]
  15. I might be reviving an old topic, but wanted to share what I have come with to run a script at a specified time of day. I have no Filemaker Server, I am running Filemaker Pro Advanced 11. In my example I want to run script "Export_DL4_Call" at 23:00:00 every day which exports data from file, let's call it "File1". I created another file, let's call it File2 on which I calculate the schedule of time and from it I call the script on File1. At first I tried with windows scheduler but it was not reliable at all. On File2 create fields "Time1" and "Schedule_Time" both as text. Create a script "Schedule_Time_24h" which runs every 24h with following steps: Set Field [File2::Schedule_Time; 86400] Install OnTimer Script ["Export_DL4_Call"; Interval: File2::Schedule_Time] This will obviously run the script every 24h, but if the file opens at 7:00 then it will run it every day at 7:00, so I created a second script as follows Create a script, which runs when file is open, "Schedule_at_23" with these steps: Set Field [File2::Schedule_Time; ""] Set Field [File2::Time1; Get ( CurrentTimeStamp )] Set Field [File2::Schedule_Time; Let ( [ hour2 = 23; min2 = 0; sec2 = 0; hour1 = Hour (File2::Time1); min1 = Minute (File2::Time1); sec1 = Seconds (File2::Time1) ]; ( sec2-sec1 ) + ( min2 -min1 )*60 + ( hour2 - hour1)*3600 )] Pause/Resume Script [duration (seconds): File2::Schedule_Time Perform Script ["Schedule_Time_24h"] The reason I am running these scripts on a second file, is because Install OnTimer Script will stop if the windows from which it runs closes, so to avoid that, I am running it on a different file which is not accessible to users.
×

Important Information

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