Database abstraction layer for WinBinder: Yes or no?

Hi all, I have another interesting question for you. One of the principles for this project is to encapsulate complex Windows things. In the beginning assumed that it should do the same with databases. Another advantage is that this method will isolate programmers from MySQL (but not prevent them to use it if they want to, of course). So I started to create a database abstraction layer or library (DAL) for WinBinder. However I know that many users don't like DALs. So what do you think? Should WinBinder... 1) ...use an existing DAL like ADOdb and maintain the original class/function names? 2) ...use an existing DAL and mask the class/function names with WB-like functions e.g. wb_create_record()? 3) ...create a new DAL with WB-like functions e.g. wb_create_record()? 4) ...ignore databases and let each user choose whether to use or not a DAL?