5 posts in this topic
We have need for a filemaker developer/consultant to make modifications to an existing Filemaker 12 database. The database makes use of a number of scripts to "synchronise" records with a second Filemaker database hosted on a windows web server.
Changes to be made to the database include debugging the existing scripts and fixing bad design in the table relationships.
The primary database is hosted in north queensland, Australia. However due to the remoteness of the location we are expecting that it will be necessary to work remotely with a developer. Access can be provided via VNC or LogMeIn. Ideally we'd like someone in a time-zone close to the East coast of Australia (and ideally within Australia), but we are willing to consider offshore developers as well.
I am an experienced web and database developer with other technologies, and I would feel most comfortable with a Filemaker developer who also had experience with SQL databases (I don't mind which ones: SQL Server, Postgres, MySQL, Oracle etc) and other programming or scripting languages in addition to Filemaker.
In addition to a series of one-off changes to the database, we would be interested in someone who can provide ongoing support.
If you are interested, please leave your contact details here, or send me a private message for more details.
By Franco Pagano
Fms 15, elcaptain, macbook air
client ipad mini 2 ios last update
i set the numeric keyboard touch for a numeric field.
it work using filemaker go, using web direct the keyboard is always the standard alfanumeric keyboard.
I tested some other filemaker example and the numeric keyboard doens't came up.
does it is normal or is a web direct "bug"?
I have a setup with fms13 running on a network that is using an Airport Extreme as router, wifi and firewall. It has worked perfectly for years. However it started playing up recently so I tried to setup a new configuration for the Airport Extreme where I opened all the ports that I thought needed to be open for FMS13 to work : 80, 443, 5003, 389. What is weird is that if I install the new setup in the Airport Extreme web direct does not work. I know that it actually functioning in FMS as I can test it locally. If I install the old setup in the Airport Extreme web direct does work, however after a few minutes the Airport Extreme becomes inaccessible, and I fear unreliable, as you can see in the attached image. Would someone know what I am missing here?
We have a newly deployed OS X 10.10.5 Server with FMS14 installed with only 3 databases hosted, all accessible via Web Direct.
Now some of our customers are experiencing difficulties with even accessing our solutions, which we have narrowed down to local network problems at our customers.
The problem is, the login window is not showing, and therefore they can't access the databases.
I then tried to connect to the database through Chrome, which worked perfectly fine!
Is there something I can do for the customer or on our Server, to prevent this message for future customers?