4D v13Video script |
||
|
4D v13
Video script
Video script
Now we're going to learn about using a database in client/server mode. Up until now, we've been programming in single-user mode; so let's look at how it works in client/server mode:
And we see that in client mode:
Since 4D is multiplatform, the same server can distribute information to both Mac and Windows machines:
We can modify an intervention on Windows, and we'll immediately see those same modifications on Mac and vice versa. The server also automatically manages record access conflicts. If we are editing a technician record and we want to open the same record on another client machine:
So much for data in client/server mode. It just so happens that our development (tables, forms, methods, etc.) is also data: this is the programmer data. The server also manages the impact of changes made on different machines, as well as the locking of "programmer" records. Here, the [Intervention] input form is open; if we switch to Windows and finish; it opens the same [Intervention] input form but specifies that another user is currently working on it. If we hit OK, a lock indicates that the form is currently being used on another machine. If we close the form on another machine and we go back to Windows, we can unlock the form by clicking on the padlock and then we'll be able to edit it. The same principle applies to the structure:
This means that a team can develop simultaneously since we have access to:
Naturally, any changes made in client/server mode can be used again in single-user mode since it's still the same structure and data. This quick approach lets you see that is quite easy to develop either in a single-user environment or on several machines directly in client-server mode. |
PROPERTIES
Product: 4D |