Currently, there is no way to share a setlist (not an exported PDF or HTML file) with another setlist maker user other than by exporting the entire database and sending a sqlite file.
I know that one of the selling points of Bandhelper is that it offers cloud database syncing and is meant to be an upgrade path from Setlist maker. However, sharing setlists manually as opposed to the whole database seems like that should be a basic feature of the app. It still differentiates itself from Bandhelper in that it's still a manual process and not cloud based.
A set list contains links to songs, breaks and pauses, and a song contains links to documents, recordings, tags and custom fields. It wouldn't be practical to share just a set list without sharing all the other connected data.
The only data that would need to be shared would be the songs, breaks and pauses. Things like MIDI presets, your layouts and your general settings would not.
Is it not possible to separate just those components from the rest of the data base?
The way databases work is that all those links are based on internal IDs; therefore the whole database needs to be copied so the IDs match. If a set list was shared across different databases with different IDs, then you would have to match songs based on their names. Then any typo or variation in spelling or duplicate name would break it.
You can use the Share Set List function to output a simple printable list of songs and related fields. But to share an interactive set list that has full functionality within the app, you need to share the whole database.