SoftPro Developer Forum

...either create a new order or overlay an existing order, depending on whether a current order matching a Loan number exists. Unfortunately, with the 2.6 version of the API, there is no way to search orders. You must connect directly to our database to find the order numbers that you want to deal ...

There are messages available on the IOrder. You can examine their Level to see their severity, and act accordingly: using (IOrder order = OrderStore.NewOrder(spec)) { try { // Manipulate your new order here foreach (IOrderMessage message in order.GetMessages()) { MessageBox.Show(message.Text); } if ...

That behavior has been marked as a bug. It will be fixed in service pack 3.

I do not know of a way to use Boylan to do this directly, but you can probably get a pretty good estimate by looking at your SQL Server information or your licensing information. Since all of our individual users in Boylan connect directly to the database, you could start capturing your average/max ...

I do not believe that it requires VS 2008 anymore. You should be able to use the Select 3.0 SDK in VS 2010.

Try setting OrderCreationSpec.BaseOrderNumber instead of OrderCreationSpec.Number. "Number" actually becomes a combination of the prefix, baseOrderNumber, and suffix.

I believe you might just be attempting to use the wrong property. I took our previous example and added the setting of the RecievedBy property: Using order As IOrder = OrderStore.NewOrder(spec) Try Dim DynOrder As Object = order DynOrder.Project = "Setting a simple string property." DynOrd...

You might need to supply a larger code sample so that we know what "identity" is in your example. First though, could you repost this question as a new topic since it appears to be unrelated to the rest of the thread. This will ensure that your question is more visible.

I did find another workaround that might help. We do support a few string methods that can be used against our IQueryable<> collections: Contains(), StartsWith() and EndsWith(). So, you can use these methods to avoid the direct string comparisons that are causing the problem. You could rewrite your ...

We were able to reproduce this behavior. It's an issue when using string comparisons against IQueryable collections using Visual Basic. Unfortunately, the only workarounds we can think of are going to be using C# instead of VB, or to avoid string comparisons in a expression like this. We have logged...