Copying the database file to a “Working” folder On iOS, the only change is that you’ll have to choose the icon with an iPhone picture in it in order to access the Build Step contextual menu in addition to the fact that every added resource needs to be signed with a certificate.Ģ. When you’re working with a Web project, you’ll find exactly the same behavior, even if you choose to deploy with Xojo Cloud. Of course, don’t forget to add the database file itself using the buttons on the Build Editor toolbar. For example, a good Destination option would be “Resources Folder”. In fact, the Destination menu contains a number of typical paths (or most relevant folders). The previous action will give you access to the Inspector Panel for the just-added item where you will be able to type a name for the Build Step, choose if the copy file action will be executed both for debugging or deployment and, most importantly, choose the location where the file should be copied when the app compiles. In order to add a new Build Step in a Desktop project select the target in the Build Settings then, from the contextual menu, choose the “Add to Build Settings > Build Step > Copy Files” option.

Bonus: Doing this allows you to decide to use different paths when debugging or deploying your app. This way, the file will be added automatically to the folder of your choice every time you compile your app. You can do that in several ways, but usually it’s best to add a Build Step. You probably created your SQLite database file using an external editor so first add that file to your Xojo project. This tutorial will show you how to deploy your SQLite based projects so they behave right on Desktop, Web and iOS, copying the database file to the right place on every target.

Xojo sqlite