Reader's Clinic - Page Marks in Windows
Database Graphics Toolkit - Blackhawk Data Corporation by Mark Hirst
Reader's Clinic - Incorrect Indexes
Vroom
RTP Series - RTP20
RTP Series - RTP12
Form.List.S
VERBatim - V5
@ATTACK - @Last.Select.Process
@ATTACK - @Save.Select
QTIPS - File Variable of File In SELECT Statement
QUERY.SUB
REVMEDIA Revisited
QTIPS - Extended Select Syntax
Spindex - A Review
Spindex vs BondTRV
REVMEDIA Revisited
QTIPS - Replacing GAS.BAR routine during PERFORM "SELECT"
QTIPS - Extended Select BY
QTIPS - EasyWriter
QTIPS - MFS - Select.Index
Report Professional (TM) - Dialog Software
R3 Report Writer Reviewed by Richard Guise, CSS Ltd
Reader's Forum - Numeric Precision in R/Basic - Hal Wyman
@ATTACK - @Default.Stops
QTIPS - Stop Lists
Reader's Clinic - Stop Lists
QTIPS - Default Stop Lists
QTIPS - Manipulating XREF formulae.
RTP5 and RTP51
RevTi Just Wanna Have Fun
Reader's Forum - Numeric Precision in R/Basic - Hal Wyman
Reader's Clinic - Naming Routines
Reader's Clinic - Prompting for Passwords
Reader's Clinic - Removing "Searching Cross References" Message
Message
Trapping Message Calls
A RevTechie Replies - And Miscellaneous Jottings - Mike Pope - Revelation Technologies (UK) Ltd
QTIPS - Standardising Error Message Display
QTIPS - Interrupt Proof Error Messages
QTIPS - Improving the Message Window
Version 3 Technical Highlights - New Message Types
Playing with Scan Codes
QTIPS - Compiling Protection Code
QTIPS - Invalid Code and Command
QTIPS - Code/Command Help
Compiling 64K on a Shoestring by Blaise Wrenn (LexStat Systems Ltd)
@ATTACK - @File.Error
@ATTACK - @File.Error.Mode
@ATTACK - @Last.Error
A RevTechie Replies - And Miscellaneous Jottings - Mike Pope - Revelation Technologies (UK) Ltd
RTP5 and RTP51
QTIPS - Standardising Error Message Display
QTIPS - Interrupt Proof Error Messages
Version 3 Technical Highlights - ValidateName
QTIPS - Using @Upper.Case and @Lower.Case with Foreign Languages
@ATTACK - @Lower.Case
@ATTACK - @Upper.Case
Sorting out Collation Sequences by Mike Pope
@ATTACK - @Help.Level
Vroom
RTP Series - RTP32
Utility Diskette # 3 - Part I
Window or Not ?
Vroom - Window Processing
QTIPS - Window Symbol Tables
VROOM - Window Processing II
@ATTACK - @HW
Uncommon Knowledge - WC_Reset%
Reader's Clinic - Related Windows
Window or Not?
Reader's Clinic - Scribe Replace Processes in Window
Soft Windows
QTIPS - Window Bug and Debugging Window Bug
Overlapping Windows And Window Menus
QTIPS - New Catalyst Option
QTIPS - Collectors on the fly
QTIPS - Blank Menus in Windows
QTIPS - Moving Objects the EASY way.
Relational Indexes - Reordering
QTIPS - Embedded SQL
QTIPS - Compiling Protection Code
A RevTechie Replies
QTIPS - DOS File Names
DOS Interfacing (Part II)
VERBatim - V116
@ATTACK - @Pri.File
@ATTACK - @Rollout.File
File Variables
How Indexes Are Updated
Index Record Layouts
QTIPS - File Variable of File In SELECT Statement
QTIPS - Amending non-Attached Files
LINEAR HASH FILE STRUCTURES - Part 1
Index Flush
QTIPS - File Handle Structure
Reader's Clinic - Page Marks in Windows

RevMedia FKB

DocumentV3I3A3
TitleQTIPS - Embedded SQL
KeywordsSQL
PROTECT.MFS
TextMark Hirst the author of the excellent graphics routines on the current
diskette writes as follows

"The embedded SQL statement

EXEC SQL SELECT CLI SUM(RES_T) SUM(CALL_T)
INTO :RECORD FROM CALLS WHERE DATE
BETWEEN :START_DATE AND :END_DATE
GROUP BY CLIENT
END EXEC

should work fine and yet just as it seems to be ready to report issues a
message saying that it cannot sum non numeric data!

After CHANGING the dictionaries and so forth nothing could stop these
frustrating messages even when the RES_T and CALL_T columns had been
redefined as INTEGER DURING my investigation I went back to TCL and used
the equivalent SQL there As the STATEMENT was executed the "Compiling
Protection Code" message appeared and the STATEMENT worked the same one!
The COMPILING Protection Code message is triggered when a change in the
dictionary is detected and an SQL STATEMENT is attempted It appears that no
such trigger takes place when executing embedded SQL My conclusion is that
the non numeric error in this case really meant a discrepancy in dictionary
type in the definition of the field and the Protection Code The solution is
to run an SQL STATEMENT FROM TCL or SQL window to force the Protection Code
to be recompiled then your embedded SQL should work "

It seems possible that this was caused by PROTECT MFS not being attached to
the file thus not keeping %PROTECT_SPEC% in sync WITH the dictionary
definition To avoid this ensure that PROTECT MFS is installed on all files
on which it is intended to do embedded SQL


(Volume 3 Issue 3 Page 10)
[revmedia/copyrigh.htm]

Page last modified: 08/02/03