[MaryTheG(r)eek]

Originally Posted by Lionel

I did not say photopost. I said PhotopostVBGallery which is different and unlike photopost is 100% vb integrated.

Really I didn't knew that there is different module. Reading Photopost I thought that it was that terrible (in support) script. And I'm wondering how they didn't started shouting because someone used the word "Photopost".
Well, I want to make clear something for all my current and future modules. I dont plan to follow the way of any type integration. The reason is very simple. Any time when the other module change something, I must follow their changes. And if they're real proffesional maybe they'll give me all the neccesary information. But imagine, I asked for vbAdvanced some documentation on how to port my module with vbAdvanced and one month now I have no reply. Imagine that I'm a commercial customer of their Links module.
I read somewhere here a very,very real topic. Is from the Author of WebMail module. He became crazy when he has to change his code with any new version of vB. Why to place myself in troubles? Why eg to use vbmail() to send an email while I can easily use mail()?