Firstly, this subject is a bit out of my depth...but then I got interested in it just last week after seeing this thread. I have since looked into it and come across the following interesting URL's.
http://msdn2.microsoft.com/en-us/library/317sza4k(en-US,VS.80).aspx
http://msdn2.microsoft.com/en-us/library/f1kyba5e(en-US,VS.80).aspx
Looking at the example code, it seems to me that to create a LLBLProvider, you would need to replace the ODBC API and SQL with LLBL equalant. Is that not the case?
For example, method
Public Overrides Sub CreateRole(rolename As String)
creates instantiates a OdbcConnection and OdbcCommand objects, stuffs the insert SQL, sets up the params, then Open(), and ExecuteNonQuery().
What are issues if all this is replaced with LLBL, i.e instratiate a roleEnity, set attrbutes, and then save.
Or am I missing something.