Search results for query: *

Don't know what is causing the fantom decimal points, but it appears they can be gotten rid of by explicitly using \#0 after the mergefield name.

Hi. I've got a mail merge doc where almost all the merged numeric fields show decimal points after I perform a mail merge (i.e., "3."). I am using Word 2002, SP3. I am using an Access file to do the mail merge. The numeric fields have zero decimal places. I have other mail merge docs that do...

Might check the DSN, if one is associated. In Access, I linked an as/400 file, using a iSeries Access DSN. On the Server tab, I changed the naming convention to -- SQL naming convention (*SQL) And I got rid of that error.

With the SQL commands: DROP FUNCTION CREATE FUNCTION DROP VIEW CREATE VIEW And the option to specify EXTERNAL objects -- Is there a way to specify a library for each (i.e., CREATE FUNCTION MYLIB/MYFUNC), without having to do it on the CREATE, etc. statements? I see where that you can create...

...I value your opinions. Just pointing out what I did. wrkobj pgmrutool/bbrlststs shows -- Object Type Library Attribute BBRLSTSTS *SRVPGM PGMRUTOOL RPGLE BBRLSTSTS *MODULE PGMRUTOOL RPGLE Which I created with CRTSQLRPGI (for the *module) and CRTSRVPGM (for...

...function work at all (with STRSQL) if it wasn't? I talked to IBM about this, yesterday, because I was racking my head, and they indicated that -- * Functions based on "Language SQL" will create service programs of type CLE. * Functions based on "Language RPGLE" will somehow be wrapped up in...

...Nicely, I get this message: CREATE FUNCTION statement complete I am able to run the function in STRSQL and get the desired result. But when I search for the object, using -- WRKOBJ PGMRUTOOL/BBFLSTSTS - or even - WRKOBJ *ALL/BBFLSTSTS The *SRVPGM does not exist.

I think you're right, Mercury2. I walked through this stuff with IBM, just a bit ago, and I changed the prototype parameters to packed fields, and the SELECT for F1 worked. (Through debug I could see the values being passed.)

Thanks. But under debug -- Fl( DEC(x.bppyer), DEC(x.bppcnb) ) - and - Fl( DEC(x.bppyer,2,0), DEC(x.bppcnb,8,0) ) Still pass along garbage data to P1.

Thanks for the replies. Unfortunately, I get the following message: NUMERIC in *LIBL type *N not found.

Thanks. I did do that. I debugged P1 running under the service job for the SQL function. I see what's going on -- the parameters coming into the procedure are being filled with garbage. (Does that somehow have to do with the return value on the procedure interface?)

Rats, you're right. The SQL select statement should read: select x.bppyer, x.bppcnb, Fl(x.bppyer, x.bppcnb) from bplib/bp300ap x where x.bppyer = 05 and x.bppcnb = 71 I don't see an SQL msgid, but rather a message at the bottom of finished statement in STRSQL that reads as...

Sorry for the bother. I have an SQLRPGLE based service program that "works" when called from an RPGLE based program, but when the same service program is wrapped in an SQL function, then used within STRSQL it fails with a data decimal error. I don't know how much info would be sufficient...

Thank you so much for your timely reply. The usage of the char function (i.e., Select bbfappsts(CHAR('XX')) ) works! I will keep your other pointers in mind.

...that I created from an RPGLE service program, but when I go to run the function through a select, I get the following error -- BBFAPPSTS in *LIBL type *N not found The function was created from the SQL Command: Create function pgmrutool/bbfappsts (PIN char(2)) Returns char(5)...

Don't know if it has been posted anywhere else at tek-tips, but discovered from one of the news group forums that changing a registry value could remove the timeout factor -- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\ODBC (QueryTimeout) Had it set at 60. Changed it to 0. Was able...

Turns out that this problem had nothing to do with VBA. It was a matter of the shared "styles" in use between multiple documents.

I have a macro in a Word 2000 document that does a few things (partly of which) -- * Creates a blank document. Documents.Add * Inserts between two and ten documents into it. Selection.InsertFile FileName:=PlanCheckCoverDoc, Range:="", ConfirmConversions:=False, Link:=False, Attachment:=False...

It appears that in test with Access XP, you can export the linked table from one db and then import it into another. http://support.microsoft.com/?kbid=208991

A couple questions of ignorance: (1) As far as the Microsoft resolution is concerned -- On the File menu, point to Get External Data, and then click Import. Import all tables, queries, forms, reports, data access pages, and macros to the new database. What if your mdb only has linked tables...