Guidelines for Software Customization and the Database

• All objects are stored in the database.

  When using programs such as MS Access, you may link the tables from MS SQL, but you cannot save the data in MS Access.

• You cannot modify <Company> objects.

  You therefore cannot modify the code of procedures or triggers. All modifications to <Company> objects will be lost after an update is carried out.

• Comply with the naming rules.

  All customized objects start with an <S>. The customer number is part of the name. Please refer to the appendix to this help.

• Use of UDTs (User Data Types).

  You cannot use the existing <Company> UDTs. This would create conflicts when converting the database.

• Rights

  By default, the application uses two right groups. This method is also used for all custom objects that are created.

  • Reader Read only

    grant select on <object> to Reader

  • User All rights

    grant all on <object> to User

• Relationships

  You cannot create foreign key constraints.

• Database updates

  Whenever there is a database update or conversion, custom objects will not be updated. These must be updated separately after conversion. This means that the functioning of the custom software cannot be guaranteed after an update.

Custom Software and Database Conversions

The presence of any custom software will not be taken into account when a database conversion is carried out. This means that, following a conversion, the functioning of the custom software depends on the nature of the database changes. When there is an update, it will be accompanied by a detailed overview of changes to the database. These changes must be checked to determine whether modifications are required to the custom software.

Object Naming Conventions