You are right!  This may work only in special situations.

I reproduced your case simplified.

SQL inbound adapter keeps a list of processed ids:
if your id is in there it is skipped. Could be there is some other trick but not as in docs. 

the list looks like this

ENSDEMO>zw ^Ens.AppData("SQLservice")
^Ens.AppData("SQLservice","adapter.sqlparam","%LastKey")=198
^Ens.AppData("SQLservice","adapter.sqlrow",196)=1
^Ens.AppData("SQLservice","adapter.sqlrow",197)=1
^Ens.AppData("SQLservice","adapter.sqlrow",198)=1
^Ens.AppData("SQLservice","adapter.sqlrow",199)=1
^Ens.AppData("SQLservice","adapter.sqlrow",200)=1
^Ens.AppData("SQLservice","adapter.sqlrow",201)=1
^Ens.AppData("SQLservice","adapter.sqlrow",202)=1
^Ens.AppData("SQLservice","adapter.sqlrow",203)=1

Manually removing it fixed my demo.

according to your description I'd  rather assume that you look for this functionality, especially concerning %LastKey

classmethod ClearStaticAppData(pConfigName As %String)

Clear static data for a config item. This is normally used to store already-processed status for input files, and other persistent values related to adapters, such as the %LastId for the SQL Inbound Adapter.

or 

classmethod InitializeLastKeyValue(pConfigName As %String, pNewLastKey As %String = 0) as %String 

A Compile has also an errlog parameter ist is clear that it does an inner error trapping.

ClassMethod Compile(
ByRef classes As %String = "",
qspec As %String = "",
ByRef errorlog As %String,
recurse As %Boolean = 0) As %Status [ CodeMode 
= expression ]

.
 therfore at termination it doesn't end in your catch{ }
 I think it may even react specially on RESJOB by just doing a HALT.

in a development environment, you may try to investigate this using a %ZSTOP routine

first option:

get the schema behind *.XSLX and import it using  XML Schema wizard.
It's incredible huge covering all XLS features you know and also that you don't want to know.
several hundred classes. XML Schema Wizard
I gave up by lack of understanding where to start. I'm not strong with XLS features.

second option:

use ActiveX_64  to access *.XLS
in Windows, your Studio has an Activate wizard that creates access to your local installed DLL.
so you need to have EXCEL installed on your server.

The wizard generates still a remarkable number of classes but it is more comprehensive
using them you can do Scripting in EXCEL. Activate Wizard

be careful to really get the 64bit version of the DLL
 

I remember a similar situation some years back with a rather sophisticated multilevel directory structure on UNIX.

The final solution, especially for al kind of searching in unique file names, was a class
with the filename as ID and directory, summary, creation date, last modification as properties.
The search (in SQL) out performed anything used before.

The only extra work was kind of a register at file creation/modification which happened at a moderate rate.  
+ a nightly batch job to verify and do the reality check. 

the dotted syntax works in the same routine as curly braces.
There was a different question recently with such code.

The confusion comes up when you use curly braces INSIDE a dotted section. 
as the nesting is calculated by the dots at the start of the line this causes confusion.  
So cascading and intermixing is a NoNo.

on the other hand 

Do
. line1
. line2
. line3

is an equivalent to 

{
 line1
 line2
 line3
}

-

As dots are always in sequence a move to { } shouldn't be that hard.

Though I admit: It's additional effort

It starts with the basic definition:
What is LEGACY for you?  any MUMPS dialect  (DTM. DSM, ISM, ...) ?

From the language elements, there is all included and possible. what was available in MUMPS.
Except that System variables may have some differences that need to be checked.
In general, you have enhancements at all levels: Commands, Functions, Variables

One of the significant differences is variable scoping.
In legacy MUMPS you had your partition and all variables were visible everywhere.
In COS this visibility is managed at various levels and you have to take control over the variable scope.

see this articles:
Variable scope in .mac routine?
Summary on Local Variable Scoping

Of course, interaction with external devices and peripheral is different.
But this doesn't affect programming style.

I assume you have some special techniques in mind.
For questionable cases, this forum is the place to get help at almost any level.
And often it's more than a single unique solution but a choice of variants the members offer.

 I  personally have seen code written on DSM-11 in 1978, copied to Caché and running without change.
This was core logic. Communication with peripherals needed adaption. No surprise.

An interesting combination!

But (from Sample.Person):

zNameGetStored(id) public {
Quit $Select(id'="":$listget($g(^Sample.PersonD(id)),2),1:"") }


there isn't that much to win.
If it then ends with %Save() it is kind of a prefetch of the global buffer.

I saw it mostly used instead of  %Open() loading / swizzling the whole object in memory
if just 1 specific property was required.
(A kind of direct global access in disguise) smiley