These are called primary keys and are usually numeric. When designing your tables, be sure that each one has a field with a value that uniquely identifies the record. For instance, you may want to present a list of customers that purchased certain merchandise, share customer information between businesses or compare the sales of one business to another. Doing so will make it easier to retrieve when you are combining related values in a single query. Both database engines are free, powerful and well supported by Xojo and this community.Ĭonsider keeping all the application data in a single database with many tables. If your application grows to become multi-user then PostgreSQL will likely be the best choice. Wow! Thanks for all the responses!īased on the information you provided, SQLite is likely the best choice. Thanks also Jean-Yves and Joost! I’m going to research SQLite. I’ve heard of Valentina (I found this link on YouTube last night: Installing Valentina for Xojo), but I’m still researching it. I’m definitely going to check out SQLite, as it seems to be highly recommended.

Just inputs from the user (Product name, product code, price, qty, etc.) Thanks for the recommendation. Would the separate information (separate databases) be difficult to construct? Thanks for your help!!īeatrix, I personally don’t see it becoming the GB rage, but maybe the user has a super long list to input. This business file will include the product database and also a client database, but if they wanted to add a completely separate business for the software, generating a completely new product/client database for that separate company, would that be a problem? When the user would start a new company they would click File ->New…starting a new file/company. For the software, the user will start a business file. Kem, yes, I’m creating this as part of a software for thousands to use.

Xojo database tutorial