Check-Out/In question

I noticed that when I use a table generated with the Component Creator the line is propely checked_ot with use-id and date/time. However when ending with Save or Close the Checked_out is 0 (zero) and Checked_out_time is 0000-00-00 00:00:00. This will still flag the record as checked_out. Only when a global check_in is done both fields are NULL and the checked_out flag is gone.
Why is this only with the tables created with the Component Creator? How to correct this behaviour?

Regards
Arnoud

The behavior you described with the tables generated using the Component Creator could be due to the way the database and the Component Creator's code handle the "Checked_out" and "Checked_out_time" fields.

When a record is being edited or modified, it is common practice to set the "Checked_out" field to a non-zero value to indicate that the record is currently checked out by a user. Similarly, the "Checked_out_time" field is usually updated with the timestamp when the record was checked out.

However, after saving or closing the record, the Component Creator might not be updating these fields correctly, leading to "Checked_out" being set to 0 (zero) and "Checked_out_time" to a default value like "0000-00-00 00:00:00". This could be an issue with the code generated by the Component Creator or with the configuration of the database.

To correct this behavior, you might need to investigate the code generated by the Component Creator and check how it handles the "Checked_out" and "Checked_out_time" fields during the saving and closing process. Look for any update statements or function calls related to these fields and ensure that they are correctly updating the values in the database.

If you are not familiar with the code or the underlying database structure, you might need to consult the documentation of the Component Creator or seek help from their support team or community forums. Additionally, you could check if there are any updates or patches available for the Component Creator that address this issue. PayMyDoctor Login
In any case, before making any changes to the generated code or database, it's essential to back up your data to prevent any data loss in case something goes wrong during the correction process.