<?xml version="1.0" encoding="ISO-8859-1"?>

<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>Data Access Worldwide Forums - DataFlex Technology Stack Testing</title>
		<link>https://support.dataaccess.com/Forums/</link>
		<description>A forum dedicated to discussing, testing, and shaping the future of the Technology Stack project.</description>
		<language>en</language>
		<lastBuildDate>Fri, 07 Aug 2026 21:40:48 GMT</lastBuildDate>
		<generator>vBulletin</generator>
		<ttl>60</ttl>
		<image>
			<url>https://support.dataaccess.com/Forums/images/misc/rss.png</url>
			<title>Data Access Worldwide Forums - DataFlex Technology Stack Testing</title>
			<link>https://support.dataaccess.com/Forums/</link>
		</image>
		<item>
			<title>Entities</title>
			<link>https://support.dataaccess.com/Forums/showthread.php?73456-Entities&amp;goto=newpost</link>
			<pubDate>Wed, 05 Aug 2026 15:15:09 GMT</pubDate>
			<description><![CDATA[Hi 
 
How will entities be generated? 
Will we be able to have comments for a "field" that the Studio will honour? 
 
Reason - with a 30+ year old...]]></description>
			<content:encoded><![CDATA[<div>Hi<br />
<br />
How will entities be generated?<br />
Will we be able to have comments for a &quot;field&quot; that the Studio will honour?<br />
<br />
Reason - with a 30+ year old database there are one or two:p badly named fields that it is not practical to rename, so it would be good to be able to document what the &quot;field&quot; is really used for and explain any abbreviated name (which made sense 30+ years ago to the person who came up with it).</div>

]]></content:encoded>
			<category domain="https://support.dataaccess.com/Forums/forumdisplay.php?101-DataFlex-Technology-Stack-Testing">DataFlex Technology Stack Testing</category>
			<dc:creator>Ian Smith</dc:creator>
			<guid isPermaLink="true">https://support.dataaccess.com/Forums/showthread.php?73456-Entities</guid>
		</item>
		<item>
			<title>YAFR: better Date to String options.</title>
			<link>https://support.dataaccess.com/Forums/showthread.php?73450-YAFR-better-Date-to-String-options&amp;goto=newpost</link>
			<pubDate>Mon, 03 Aug 2026 16:09:55 GMT</pubDate>
			<description>We are being bitten by regional settings for dates being handled differently in SQL server vs DF.   
 
---Quote--- 
 
 
* Raw Data shows dates and...</description>
			<content:encoded><![CDATA[<div>We are being bitten by regional settings for dates being handled differently in SQL server vs DF.  <br />
<div class="bbcode_container">
	<div class="bbcode_description">Quote:</div>
	<div class="bbcode_quote printable">
		<hr />
		
			<br />
<ul><li style="">Raw Data shows dates and times in U.S. format. Depending on your Windows Regional Settings, raw data may be displayed in a different format.</li></ul>
			
		<hr />
	</div>
</div>can we have a way to override, at the Application level, this dependency on windows regional settings?  In particular Korean seems to have an odd separator in the date time, which is represented differently in SQL server. <br />
<br />
FYI underlying cause is that we hash the concatenated string values of all the (other) fields in a table to create a hash that we use to detect tampering.</div>

]]></content:encoded>
			<category domain="https://support.dataaccess.com/Forums/forumdisplay.php?101-DataFlex-Technology-Stack-Testing">DataFlex Technology Stack Testing</category>
			<dc:creator>Michael Mullan</dc:creator>
			<guid isPermaLink="true">https://support.dataaccess.com/Forums/showthread.php?73450-YAFR-better-Date-to-String-options</guid>
		</item>
	</channel>
</rss>
