As newbie and relativly limited programmer I am unsure about which route to take. The documentation provides useful help in determining this based on application parameters (size, scope etc...).

Based on the fact I will be developing relatively small and simple applications + the fact SS entities seem easier to use, my inclination would be to go for this option.

However pretty much everyone else on the forum seems to be using the adapter model. In addition it would seem (and this is an important point for me) that most templates are being based around the adapter model. I most definately dont want to exclude myself from the excellent templates on offer (and would like to become involved if I can). Therefore in this sense the adapter model seems the one to go for?

The both option? A final option is to generate code for both options. This I suppose is a bit pointless but my question really is would there be anything in the design of the LLBLGen project itself that would stop a project being able to be generated in both scenarios?

Both is not an option, as it would be confusing what to use in which routine.

You could proceed with Selfservicing, unless your projects require a distributed architecture, then adapter is perhaps the best way to go. However selfservicing is often used in smaller projects, as it is easier to use as you said, however adapter isn't that harsh though, it requires a bit more casting, but that's about it. The main difference is the paradigm difference: persistence as a service (adapter) or persistence as behavior (selfservicing).