iBO

Converting IBOGuest in IBO.Com

I'm developing an online app for creating a new imis account using the ibo.com. I'm using .com until we go to 15.0. When I create a new account (non-member) the userid is created as IBOGuest and I read about the convertGuest method but I still not able to get a id and password established. Can someone point me in the right direction. I'm using Asp with VBScript. This is the script I have for now:

iBO version 10.5.28.01

I am looking for iBO version 10.5.28.01. Can anyone direct me to the proper download? (Is it iBO for .NET - Project 0.1 (alpha)?)

Thanks much!

iMIS 15 com iBO Subscript out of range error

We just upgraded a custom iMIS 10.6 iBO application to use the iMIS 15 iBOs, and started getting the following internal IBO error:

„Unknown error. Description: Subscript out of range” error number 1000

The error is thrown when we try to filter contact data. Here is the code causing the problem:

Private _securityAdmin As iboUserSecurity.CUser
Private _contactManagementAdmin As iboContactManagement.CContactsBOAdmin

Database Language and Date Format in iBO.COM

Problem Description
I have a problem with iBO.COM inserts in SQL 2005 on an Australian server.

We have a live and a test site, with respective databases.

The live site is showing this in the SQL trace when iBODataServer user connects. Inserts work.

- network protocol: TCP/IP
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on

SQL Function for credit card number decryption in iMIS15 and SQL2005

There is a continuing need for a SQL Function or equivalent to decrypt credit card information from iMIS.

Of course there is an overall security concern, but there still are frequent requirements by customers to have a method to decrypt credit card info, beyond the standard reporting in iMIS.

I have done a little research on this. There is just a little info on it in www.imiscommunity.com.

iBO for COM and iMIS15

My organization has a fairly extensive set of custom apps written using the original iBO for COM. We are now looking to upgrade to iMIS 15, but understand there have been significant schema changes as well as a move away from traditional COM components (.dll) in exchange for a more modern .NET setup. This is all well and good, but we may not have time to rewrite every application prior to our deployment and I wanted to know if anyone has had success using iBO for COM and iMIS 15. I can't find a single page of documentation.

New name(s) for iBO

Is it just me, or are all the "business object" named things starting to become confusing? Here's the ones I can count:

  • The original COM-based iBO
  • iBO for .NET
  • The core Business Objects which make up iMIS
  • Business Object Builder, Business Object Architect, Business Object Designer, or whatever else it becomes
  • Stephen Moseley's iBO Wrapper
  • The Active Matter iBO Wrapper

iBO Fully Paid vs. Bill Me Later

Our organization wanted to use iBO to put event registration orders entered on the web into our system. However, we hit one big stumbling block. Apparently, the iBO CRegistration class supports only fully paid registrations. Many of our customers opt to be invoiced rather than to pay on line. Therefore, we can't use iBO.

Has anyone encountered this problem? If so, how did you address it?

User authentication

I am trying to connect the iBO's (version 10) up to a website with PHP. I have successfully managed to get PHP communication to our database via the iBO's.

One thing I cannot work out from the documentation is how to authenticate a user. Can someone give me any pointers on this?

I am not sure that my logic is correct. This is the flow of my routine so far:
Create an iboUserSecurity.CUser instance

ProcessPayment in CPayment class

I am calling the ProcessPayment function in the CPayment class to process credit card transactions. This function has worked very well, but I began receiving errors from this function on a few specific users. I tracked the error down, and the ProcessPayment function itself was throwing an exception.

It turned out that the exception was being thrown when an ampersand was in the billing address.