convert filemaker to mysql

[kathys39]

I'm in the process of converting a filemaker db to mysql. What I need help with is in the interface. This is a multi-user filemaker db, one server, many clients. When filemaker boots, you can tell it whether it's the server or client, and if a client, where the data resides. The interface does all the record locking, etc.

I'm now starting on an interface in PHP. I'm assuming allI have to do is a record lock when someone does a mysql query to see, add, or delete data. Is this correct or am I forgetting something? thanks

[sad69]

The difference is that it is now like a webpage.

If you give access to 2 or more people to edit a record, if one person is editing the record, but hasn't yet saved it, and then another person starts to edit the record, the last person to save will overwrite the first person's changes.

I think locking the record will only lock it while the user is actually saving it so as to combat two people saving/accessing at the exact same time or something.

Now you might think that you should lock the record once the user enters the edit screen. Well, what if the browser crashes or they user hits the close button? Now that record is locked forever..

I'm not offering a solution, just outlining a possibility...

Sadiq.

[raf]

The interface does all the record locking, etc.

I'm now starting on an interface in PHP. I'm assuming allI have to do is a record lock when someone does a mysql query to see, add, or delete data. Is this correct or am I forgetting something? thanks
What exactly are you asking?

What the most suited lock-level is? --> depends on your situation (and even table-type which is of course a consequnece of your requirements) Only InnoDB tables allow recordlevel locking. MyIsams only allow table-locking.

[dsimpson]

I'm in the process of converting a filemaker db to mysql. What I need help with is in the interface. This is a multi-user filemaker db, one server, many clients. When filemaker boots, you can tell it whether it's the server or client, and if a client, where the data resides. The interface does all the record locking, etc.

I'm now starting on an interface in PHP. I'm assuming allI have to do is a record lock when someone does a mysql query to see, add, or delete data. Is this correct or am I forgetting something? thanks

Readers of this post may be interested to know that it is not only possible to convert the data, but also the graphical interface of the FileMaker database (Layouts, value lists, portals, vector graphics objects, script) into a functional PHP web application.

Automated Layout to PHP Conversion (http://www.fmpromigrator.com/services/php_conversion.html)

David Simpson