Following a similar instance / error I had with one of my projects.
The project contained a myriad of references to the GoogleMaps lib ... and also contained a module "Map" ... not healthy.
Following a similar instance / error I had with one of my projects.
The project contained a myriad of references to the GoogleMaps lib ... and also contained a module "Map" ... not healthy.
YOU are the AppAuthor aren´t you? You already should know what you are using in your code. If not: add a Naming regime and check for existence if you are unsure it exists.
Whilst I have a (bad ?) habit of keeping class / module names short , (ie: Map), I don't think I would resort to using 2 letter initials as a naming practice.
But this is now all in hind-site ....
mDataBase , clsDatabase ... but would you not then immediately turn round a type Dim DB as clsDatabase
YOU are the AppAuthor aren´t you? You already should know what you are using in your code. If not: add a Naming regime and check for existence if you are unsure it exists.
In this case, I had an app built before I needed to use DBUtils. So, having a class named DB was no problem. It wasn't until I added that library that the problem arose. Not sure how I was supposed to avoid using a class name that was going to cause a conflict in the future with a library I didn't know I was going to use.
But, you're right! I need a better naming scheme anyway! "DB" is a horrible class name!