XAPI return values are blank

[Bluejay07]

Hello,

I have a program which has worked for years in various environments. This program uses xapi and has recently been installed on a client's machine.

I'm assuming this issue is environmental since no one else has encountered this issue, however, the values that are being returned from an xapi call are blank.

Here's the situation: a user clicks a finder which sets up a form displaying the accpac information. The query results display fine, however, I am receiving blank header information when the FinderFields function is being used. Since the code is very spread out, here is a small sample:

Public FinderFields As ACCPACXAPILib.xapiFields

...

   With myFinderForm.FinderGrid
      For i = LBound(FieldCols) To UBound(FieldCols)

[red]
*** This section returns a blank string.  ***

         .TextMatrix(0, i) = Trim$(FinderFields(FieldCols(i).ColName).Description)

*** Eg. Trim$(FinderFields("NAMECUST").Description) = ""
*** It should be ... = "Customer Name"
[/red]

         .ColWidth(i) = FieldCols(i).ColWidth
         .ColAlignment(i) = FieldCols(i).ColAlign
         l_lngWidth = l_lngWidth + .ColWidth(i)
      Next i

The client is using Accpac 55, SQL 2008 and Windows Server 2003 Standard Edition.

From what I can tell all sections (ODBC, database and permissions) seem to be configured correctly.

As mentioned, this has never been an issue until this install. Does anyone have any suggestions on what might be causing this to happen?

As a separate issue, this same client is running another program and the accpac error handler returns a blank description. I'm assuming these issues are related, but I haven't found a cause or solution.

If at first you don't succeed, then sky diving wasn't meant for you!

 

[Bluejay07]

Not to my knowledge. I believe only accpac 55 is installed and all service packs seem to be up to date.

If at first you don't succeed, then sky diving wasn't meant for you!

 

[Bluejay07]

My boss (who is a senior accpac consultant) thinks that the cause might be because of Accpac 55 running on SQL server 2008. Any thoughts on this?

If at first you don't succeed, then sky diving wasn't meant for you!

 

[ettienne]

It's not the db version, it's actually irrelevant in this case. He's a senior accpac consultant and he thinks that?

 

[Bluejay07]

Thanks ettienne. Yes since 55 was designed to work with 2005 and 56 design for 2008. We are just trying to eliminate any possibility.

If at first you don't succeed, then sky diving wasn't meant for you!

 

[ettienne]

Who says it was designed for a specific version of SQL?
Anyway, install SQL 2008 and 5.5 on a test computer and verify of that is the problem. Remember it's your application that is upchucking, no one else is really going to be able to help you. And you are still using xapi...

 

[Jay Converse]

He's a "senior" Accpac consultant? Does that mean experienced, or just old? That's the best LOL I've had all month.

This is a language DLL problem, that's where the field descriptions are stored. That's why the question about multiple Accpac versions was relevant.

 

[DjangMan]

If you log on to Accpac as the user that the application logs on as does Accpac look normal? I've basically run out of ideas. Oh - one more: Format C.

 

[ettienne]

Format C.... that's my line

 

[Bluejay07]

Thanks for all of your comments and suggestions.
I was using the ADMIN account for both Accpac and the application with the sa ODBC connection. All appears normal.

Somehow I don't think the client will take the formating option.

If at first you don't succeed, then sky diving wasn't meant for you!