Naming Recomendations for Base Objects?

Does anyone have recommendations for the best way to name objects in a Base file? When I say “Objects” I mean any Base object such as tables, fields, forms, controls, queries, labels, etc. There doesn’t seem like there is any consistency in any of the example Base file I have viewed.

I know being consistent in naming things will likely make the objects easier to remember down the road when creating queries, forms and reports which use those objects.

Is there anything in particular to avoid that could create problems later in development of the database?

I come from a background of using MS-ACCESS for several decades and although it is over twenty years old and applies to VBA I try to follow the Reddick Naming Conventions. They are very comprehensive and adaptable.

If more than one person is going to maintain your application and/or it is likely to develop and grow I advocate that you adopt and stick to a convention. It’s a worthwhile long term investment and it will payoff.

Hi Jim, in the documentation, I think you can find useful information:

https://wiki.documentfoundation.org/Documentation/Publications#LibreOffice_Base_Guide
https://wiki.documentfoundation.org/Documentation/Publications#LibreOffice_Base_Handbook
https://wiki.documentfoundation.org/Faq/Base

There are no rules, Base works anyway.
These are the examples that I use:

T_TableName

Q_QueryName

F_FormName

FieldName

I do not use interruptions in the names to create no problems in their use in the code.

If this helps then please tick the answer (:heavy_check_mark:)

As an additional consideration, make each of your fieldname unique. Especially a primary key that is linked to a foreign key. Primary Key → issuePK Foreign Key → issueNUM

I also find it helpful to include the type of Control in the name of the field, as a reminder when invoking in a Macro because the methods and properties for the various controls are different. Thus txtFirstName and numPriKey and dtBirthday and lblBirthday.