I've been using the product for a few months now w/ great success. Recently, we decided to use LLBLGen for another project. I had been using it for project A for many months without issue. So a couple of days ago, I started using it for project B. Today is the first day I've had some code and a database w/ test data to test against. So basically, this the first time LLBLGen had to do anything for project B. The first call to load a collection generates a System.NullReference. I have no idea why. Here's the code:
adapter = new DataAccessAdapter(ConfigurationSettings.AppSettings["DSN"].ToString(),
false, CatalogNameUsage.ForceName, ConfigurationSettings.AppSettings["CatalogName"].ToString());
IRelationPredicateBucket filter = new RelationPredicateBucket();
filter.PredicateExpression.Add(PredicateFactory.CompareValue(EPS_ProcessSourceFieldIndex.Name, ComparisonOperator.Equal, name));
EntityCollection processSourceCollection = new EntityCollection(new EPS_ProcessSourceEntityFactory());
// crash, bang, boom!
adapter.FetchEntityCollection(processSourceCollection, filter);
The database schema for EPS_ProcessSource is as follows:
ID_ProcessSource int
Name varchar(50)
Description varchar(50)
There are only two records in that table and there are no nulls.
One item of interest, when I did some comparing and contrasting between the program that works fine w/ LLBLGen Pro and the one that doesn't, I noticed something a little peculiar. After the constructor call to RelationPredicateBucket, in the system where it doesn't work the members PredicateExpression and Relations both have "System.ArgumentException" when I view them in the debugger. In the system where it works, they do not.
There's not much going on here, so I'm completely at a loss.
P.S. Project A and Project B use two different databases.
