Jump to content

TinBane

Members
  • Posts

    6
  • Joined

  • Last visited

TinBane's Achievements

Rookie

Rookie (2/14)

  • First Post
  • Conversation Starter
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. So I'm running Mac OS X. The ODBC driver is on mac os x, as is the python code. Server is Mac OS X too. Is there any way to get an SQL log from FMS 11? for xdbc?
  2. I'm using pyodbc to send SQL queries to a filemaker 11 server. I can read data, no problem. I can update data, no problem. But when I attempt to insert data, no errors are thrown but no records are added to the database.
  3. I've worked out select window, which brings the window to the front. I then want to run a find, but it seems like if I tell it to run a find, it does it on the other file I have open. If I call a script on the other file, to run the find, with the script parameter being the ID of the record to pull, it seems to pull no record. Weird. Is that normal behaviour, or should one (or either) of these options do what I want?
  4. Hi Guys, I'm running a system that involves switching between two files. If I've got a window from another file open in the background, how can I tell filemaker to select that window, and select a record then run a script on it?
  5. That's fantastic. Modal windows fulfill the requirements of the database much better than standard 'live' windows. The only reasons the current windows are live, is because they were created that way, by someone else who presumably didn't know about modality. It's good to know the filemaker term for it too! Thankyou VERY much!
  6. I'm working on a database that is used in a production environment. One workstation in particular, is notorious for having 50+ FMP windows open, because they won't shut the windows when they are done with them. Is there a way to lock users out of background filemaker windows, until they have dismissed the foreground window?
×
×
  • Create New...

Important Information

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