<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Posts on Date Rpgle</title>
    <link>https://date-rpgle.pages.dev/posts/</link>
    <description>Recent content in Posts on Date Rpgle</description>
    <image>
      <title>Date Rpgle</title>
      <url>https://tse1.mm.bing.net/th?q=date%20rpgle</url>
      <link>https://tse1.mm.bing.net/th?q=date%20rpgle</link>
    </image>
    <generator>Hugo -- 0.151.1</generator>
    <language>en</language>
    <lastBuildDate>Tue, 28 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://date-rpgle.pages.dev/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Working with date rpgle Fields without Headaches</title>
      <link>https://date-rpgle.pages.dev/posts/date-rpgle/</link>
      <pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://date-rpgle.pages.dev/posts/date-rpgle/</guid>
      <description>Figuring out how to handle a date rpgle field can feel like a chore if you&amp;#39;re stuck looking at old legacy code while trying to write something modern. We&amp;#39;ve all been there—staring at an eight-digit numeric field that&amp;#39;s supposed to be a birthday,</description>
    </item>
  </channel>
</rss>
