I have finally had time to dig in and figure out what is going on with the membership provider. There is nothing wrong with the provider, and it seems to be in the database scripts. I found that when the MEMBERSHIP_CREATEUSER sp was being called, it was accepting the parameters for PASSWORDFORMAT, and PASSWORDANSWER, but they were never in the insert statement. Further more through out the entire script, the data types were not included BOOLEAN was a custom data type, and the most important key to the puzzle was that PKID was declared CHAR(16) with a character set of OCTETS, and all the sp had just been declared with a CHAR(16) value and no character set. I have included a script that has all these changed made and seem is reproducible on different machine.
All of my previous complaints have now been resolved, except the web parts profile provider which I will investigate tomorrow as I have not had enough time to test. Thank you, Steven. If you want to see/use the scripts I can email them to you [EMAIL PROTECTED] ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
