Skip to main content

A New Addition


On Wednesday, April 27th, we welcomed Isabella Lillian Spendolini into the world. She was 7 lbs 7 oz and 20". Both mom and little Izzy are doing well.

All three of us have been trying to get some rest this week. Fortunately, Grandma is in town and has taken over pretty much all day to day tasks.

Comments

~M said…
Awwww She is sooo cute!! Congrats!!!
Anonymous said…
Congratulations!!!
Niall said…
Congratulations. She's beautiful
Anonymous said…
Congratulations!!
Anonymous said…
Beautiful little angle. Congratulations!
Aman.... said…
Congratulations and best wishes sir!
Anonymous said…
Congratulations Scott. She is a beautiful girl. Wish You all the best.

Denes Kubicek
Anonymous said…
Congratulations Scott. She is a beautiful girl. Wish You all the best.

Denes Kubicek
Anonymous said…
Congratulations Scott
Anonymous said…
Congratulations Scott (and to your wife of course!).
Colin Sheppard said…
Such a pretty one!

Congratulations! :)
Anonymous said…
Many congratulations! I think the words that best summed it up for me when our daughter was born:

"No dating till you're married."
- Oscar Proud, The Proud Family

- Mark
Anonymous said…
Congrats Scott, must be one of the reasons why you're posting to the ApEx forum at 3am!

Phil

Popular posts from this blog

Custom Export to CSV

It's been a while since I've updated my blog. I've been quite busy lately, and just have not had the time that I used to. We're expecting our 1st child in just a few short weeks now, so most of my free time has been spent learning Lamaze breathing, making the weekly run to Babies R Us, and relocating my office from the larger room upstairs to the smaller one downstairs - which I do happen to like MUCH more than I had anticipated. I have everything I need within a short walk - a bathroom, beer fridge, and 52" HD TV. I only need to go upstairs to eat and sleep now, but alas, this will all change soon... Recently, I was asked if you could change the way Export to CSV in ApEx works. The short answer is, of course, no. But it's not too difficult to "roll your own" CSV export procedure. Why would you want to do this? Well, the customer's requirement was to manipulate some data when the Export link was clicked, and then export it to CSV in a forma

Refreshing PL/SQL Regions in APEX

If you've been using APEX long enough, you've probably used a PL/SQL Region to render some sort of HTML that the APEX built-in components simply can't handle. Perhaps a complex chart or region that has a lot of custom content and/or layout. While best practices may be to use an APEX component, or if not, build a plugin, we all know that sometimes reality doesn't give us that kind of time or flexibility. While the PL/SQL Region is quite powerful, it still lacks a key feature: the ability to be refreshed by a Dynamic Action. This is true even in APEX 5. Fortunately, there's a simple workaround that only requires a small change to your code: change your procedure to a function and call it from a Classic Report region. In changing your procedure to a function, you'll likely only need to make one type of change: converting and htp.prn calls to instead populate and return a variable at the end of the function. Most, if not all of the rest of the code can rem

Logging APEX Report Downloads

A customer recently asked how APEX could track who clicked “download” from an Interactive Grid.  After some quick searching of the logs, I realized that APEX simply does not record this type of activity, aside from a simple page view type of “AJAX” entry.  This was not specific enough, and of course, led to the next question - can we prevent users from downloading data from a grid entirely? I knew that any Javascript-based solution would fall short of their security requirements, since it is trivial to reconstruct the URL pattern required to initiate a download, even if the Javascript had removed the option from the menu.  Thus, I had to consider a PL/SQL-based approach - one that could not be bypassed by a malicious end user. To solve this problem, I turned to APEX’s Initialization PL/SQL Code parameter.  Any PL/SQL code entered in this region will be executed before any other APEX-related process.  Thus, it is literally the first place that a developer can interact with an APEX p