Precisely Speaking
May 21, 2012, 06:29:14 PM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: So what's news with you?  Tell us about it in "Getting To Know You"!
 
   Home   Help Calendar Login Register  
Pages: [1] 2   Go Down
  Print  
Author Topic: DDE Connect errors  (Read 2607 times)
davisd
Professional
***
Posts: 15


« on: September 16, 2010, 09:08:10 AM »

Getting the following on DDECONNECT to excel in SB+/SBClient on one customer.

DDE KEYWORD System HAS NO ENTRY IN SYSTEM DEFINITION FILE
DDE KEYWORD Topics HAS NO ENTRY IN SYSTEM DEFINITION FILE

This is SB+ 5.3.3.261.  Another customer on the same version works fine.

I get the same errors in the SBDEMO account DDE examples.

I did a COMPARE of the DMSYSDEFN on the customer where it worked with the DMSYSDEFN file on the customer where it didn't.  No difference except in stationery/printer settings.

Any ideas?
Logged
precisonline
President/Chief Technologist
Administrator
Rock Star
*****
Posts: 1532



WWW
« Reply #1 on: September 16, 2010, 09:15:40 AM »

Are both on the same version of Windows?
Logged

-Kevin
Accidents "happen"; success, however, is planned and executed.
davisd
Professional
***
Posts: 15


« Reply #2 on: September 16, 2010, 10:06:06 AM »

Both servers are AIX.

The one that it works on is AIX 5.3.  It also works on our development server AIX 5.3

The one where it doesn't work is 5.1.

My desktop is the windows client in both cases.

I would just about kill for UT.DDE source code right now.

Logged
precisonline
President/Chief Technologist
Administrator
Rock Star
*****
Posts: 1532



WWW
« Reply #3 on: September 16, 2010, 10:14:26 AM »

So the same SBClient connecting to two AIX boxes on different versions of AIX.  Okay, I get that.  Are they the same version of SB+ as well?

DDE is such a disaster, especially with SB+.  In my experience it's always easier to create a flat file and then use TU.DOWNLOAD to transfer to the client and TU.LAUNCH.APP to open it in Excel.
Logged

-Kevin
Accidents "happen"; success, however, is planned and executed.
davisd
Professional
***
Posts: 15


« Reply #4 on: September 16, 2010, 10:56:52 AM »

server version is 5.3.3.261 on the working and non-working customer site.
client is 5.3.8 on my site.
I've got the DDE working nicely right now except at the non-working site, and it works regardless of whether or not Excel is currently launched or has a blank workbook open.

We create a flat CSV file, and transfer it with L:SB.TO.DOS.

We also download a blank "xls" file and a template with macros to load and format the CSV data.

Excel 2007 is the version we are running.

The SBDEMO samples should work at least, but they get the same errors.
Logged
DonQuixote
Rock Star
*****
Posts: 108


To Dream the Impossible Dream...


« Reply #5 on: September 16, 2010, 11:03:33 AM »

Do you have   C:\temp     ??
Logged
davisd
Professional
***
Posts: 15


« Reply #6 on: September 16, 2010, 11:28:52 AM »

On the client, yes.
Logged
precisonline
President/Chief Technologist
Administrator
Rock Star
*****
Posts: 1532



WWW
« Reply #7 on: September 16, 2010, 11:30:51 AM »

davisd, can you confirm both servers are running the same SB+ server version?
Logged

-Kevin
Accidents "happen"; success, however, is planned and executed.
davisd
Professional
***
Posts: 15


« Reply #8 on: September 16, 2010, 11:50:28 AM »

SB+ 5.3.3.261 in both the working and non-working customer.
Logged
precisonline
President/Chief Technologist
Administrator
Rock Star
*****
Posts: 1532



WWW
« Reply #9 on: September 16, 2010, 11:56:30 AM »

Any chance that the TU subroutines haven't been updated on the one server?  TUBP is there and should have source code.  You might compare the line counts on TU.TO.EXCEL or TU.DOWNLOAD to be sure they're the same.
Logged

-Kevin
Accidents "happen"; success, however, is planned and executed.
davisd
Professional
***
Posts: 15


« Reply #10 on: September 16, 2010, 01:06:13 PM »

All the same.  Same date, same size.
Logged
precisonline
President/Chief Technologist
Administrator
Rock Star
*****
Posts: 1532



WWW
« Reply #11 on: September 16, 2010, 01:19:59 PM »

The compiled code is the same size as well on both systems?  Maybe one needs some recompilation?
Logged

-Kevin
Accidents "happen"; success, however, is planned and executed.
Tom Pellitieri
Rock Star
*****
Posts: 171


Tom Pellitieri - Toledo, Ohio


« Reply #12 on: September 16, 2010, 01:33:06 PM »

Recomplied, or possibly re-cataloged...
Logged
davisd
Professional
***
Posts: 15


« Reply #13 on: September 16, 2010, 01:40:26 PM »

Compiled code is the same size.
The error is displayed in the UT.DDE subroutine (for which there is no source)
None of the TU.DDE subroutines are in the stack at that point.
Logged
precisonline
President/Chief Technologist
Administrator
Rock Star
*****
Posts: 1532



WWW
« Reply #14 on: September 16, 2010, 01:44:54 PM »

I take it the error messages you're seeing are standard type 3 errors in SB+?  You might try dumping the object of that DMUT item with od -tc in AIX to see if there's any visible strings in there that might give some clues.  I would also think that DMCONT might be worth comparing as well.
Logged

-Kevin
Accidents "happen"; success, however, is planned and executed.
Pages: [1] 2   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.7 | SMF © 2006-2008, Simple Machines LLC Valid XHTML 1.0! Valid CSS!