<?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><![CDATA[Data Access Worldwide Forums - Studio & Utilities]]></title>
		<link>https://support.dataaccess.com/Forums/</link>
		<description>Discussions related to the use of the DataFlex Studio and other utilities when not specific to the type of application.</description>
		<language>en</language>
		<lastBuildDate>Sat, 17 Oct 2026 19:06:51 GMT</lastBuildDate>
		<generator>vBulletin</generator>
		<ttl>60</ttl>
		<image>
			<url>https://support.dataaccess.com/Forums/images/misc/rss.png</url>
			<title><![CDATA[Data Access Worldwide Forums - Studio & Utilities]]></title>
			<link>https://support.dataaccess.com/Forums/</link>
		</image>
		<item>
			<title>Navigation Designer</title>
			<link>https://support.dataaccess.com/Forums/showthread.php?73640-Navigation-Designer&amp;goto=newpost</link>
			<pubDate>Tue, 06 Oct 2026 23:15:45 GMT</pubDate>
			<description>Is there any intention to add filtering to the Navigation Designer? 
 
 
For even a moderately sized application the complete navigation graph...</description>
			<content:encoded><![CDATA[<div>Is there any intention to add filtering to the Navigation Designer?<br />
<br />
<br />
For even a moderately sized application the complete navigation graph quickly <br />
becomes difficult to use. <br />
It would be extremely useful to be able to right-click an object and select something<br />
 like <b>“Show navigation from here”</b> and/or <b>“Show navigation to here”</b>, perhaps with an option for one level, two levels or all.<br />
<br />
<br />
<br />
The designer is very useful in a small application, but once there are a lot of views and navigation paths, showing everything at once becomes overwhelming.<br />
Is anything like this planned?</div>

]]></content:encoded>
			<category domain="https://support.dataaccess.com/Forums/forumdisplay.php?91-Studio-amp-Utilities"><![CDATA[Studio & Utilities]]></category>
			<dc:creator>Chris Spencer</dc:creator>
			<guid isPermaLink="true">https://support.dataaccess.com/Forums/showthread.php?73640-Navigation-Designer</guid>
		</item>
		<item>
			<title>Claude or ???</title>
			<link>https://support.dataaccess.com/Forums/showthread.php?73622-Claude-or&amp;goto=newpost</link>
			<pubDate>Tue, 29 Sep 2026 17:57:58 GMT</pubDate>
			<description>Hi Everyone, 
 
I have inherrited a fairly large DF 19.1 application that I will eventually be responsible for maintaining, updating and ongoing...</description>
			<content:encoded><![CDATA[<div>Hi Everyone,<br />
<br />
I have inherrited a fairly large DF 19.1 application that I will eventually be responsible for maintaining, updating and ongoing development. There is not much internal documentation about the database structure or the application design or data flow etc.<br />
<br />
I do have human assistence in the form of the previous developers but I'd like to have some kind of resource that I can query to ask things like &quot;what does this view do?&quot; or &quot;which view is used to manage the inventory?&quot; or questions like that (but more subtle ot sophisticated probably).<br />
<br />
I'm thinking that this is a job for AI<br />
<br />
Any of you out there have any advice on which AI system to use, how to train it to know about this application, or any advice really to get started with that. It would be good if the agent also understands DataFlex of course....<br />
<br />
best - John van Houten</div>

]]></content:encoded>
			<category domain="https://support.dataaccess.com/Forums/forumdisplay.php?91-Studio-amp-Utilities"><![CDATA[Studio & Utilities]]></category>
			<dc:creator>John van Houten</dc:creator>
			<guid isPermaLink="true">https://support.dataaccess.com/Forums/showthread.php?73622-Claude-or</guid>
		</item>
		<item>
			<title>Package Manager Playground / Test Area ?</title>
			<link>https://support.dataaccess.com/Forums/showthread.php?73606-Package-Manager-Playground-Test-Area&amp;goto=newpost</link>
			<pubDate>Wed, 23 Sep 2026 13:24:26 GMT</pubDate>
			<description><![CDATA[Is there any test area in terms of creating, and managing server packages, besides the official LIVE one  ?  
 
I don't feel comfortable with the...]]></description>
			<content:encoded><![CDATA[<div>Is there any test area in terms of creating, and managing server packages, besides the official LIVE one  ? <br />
<br />
I don't feel comfortable with the process, and I don't want to create a mess in the official env.  <br />
<br />
and if yes, a how-to guide would be very welcome.  <br />
<br />
I remember something from the FlexRoads trainning, that we configured studio to a diff env, but we don't have the slides and the procedure used as a reference.  <br />
and not sure if that env was setup just for the training or not..  <br />
<br />
anyway...  a test env would be very welcome in my opinion to make user more confortable with the process..</div>

]]></content:encoded>
			<category domain="https://support.dataaccess.com/Forums/forumdisplay.php?91-Studio-amp-Utilities"><![CDATA[Studio & Utilities]]></category>
			<dc:creator>Samuel Pizarro</dc:creator>
			<guid isPermaLink="true">https://support.dataaccess.com/Forums/showthread.php?73606-Package-Manager-Playground-Test-Area</guid>
		</item>
		<item>
			<title><![CDATA[DF 26 - Pkg Mgr - Allow select & copy text]]></title>
			<link>https://support.dataaccess.com/Forums/showthread.php?73600-DF-26-Pkg-Mgr-Allow-select-amp-copy-text&amp;goto=newpost</link>
			<pubDate>Mon, 21 Sep 2026 23:52:53 GMT</pubDate>
			<description>3rd party packages, will place urls at description tab, and at the  right-side deck, to instruct developers to the main documentation, or how to use...</description>
			<content:encoded><![CDATA[<div>3rd party packages, will place urls at description tab, and at the  right-side deck, to instruct developers to the main documentation, or how to use their packages. <br />
<br />
<br />
We can't select &amp; copy such urls today.     <br />
<br />
Even better, if the description supports  markdown, so we could add real and clickable links out there.  <br />
<br />
This is the case for the WEBAPIS  package from Kruse-Net publisher for example.  <br />
<br />
<a href="https://support.dataaccess.com/Forums/attachment.php?attachmentid=18337&amp;d=1790034762"  title="Name:  DF26_pkgMgr_links.png
Views: 26
Size:  87.9 KB">DF26_pkgMgr_links.png</a></div>


	<div style="padding:10px">

	

	

	
		<fieldset class="fieldset">
			<legend>Attached Images</legend>
			<ul>
			<li>
	<img class="inlineimg" src="https://support.dataaccess.com/Forums/images/attach/png.gif" alt="File Type: png" />
	<a href="https://support.dataaccess.com/Forums/attachment.php?attachmentid=18337&amp;d=1790034762">DF26_pkgMgr_links.png</a> 
(87.9 KB)
</li>
			</ul>
			</fieldset>
	

	

	</div>
]]></content:encoded>
			<category domain="https://support.dataaccess.com/Forums/forumdisplay.php?91-Studio-amp-Utilities"><![CDATA[Studio & Utilities]]></category>
			<dc:creator>Samuel Pizarro</dc:creator>
			<guid isPermaLink="true">https://support.dataaccess.com/Forums/showthread.php?73600-DF-26-Pkg-Mgr-Allow-select-amp-copy-text</guid>
		</item>
		<item>
			<title>Package Manager (Lib +  Sample)  approach ?</title>
			<link>https://support.dataaccess.com/Forums/showthread.php?73599-Package-Manager-(Lib-Sample)-approach&amp;goto=newpost</link>
			<pubDate>Mon, 21 Sep 2026 21:27:16 GMT</pubDate>
			<description><![CDATA[in old (or current)  days,  when we would "share" a lib,   normally we would share 2 workspaces..   one for the lib it self, and another one for a...]]></description>
			<content:encoded><![CDATA[<div>in old (or current)  days,  when we would &quot;share&quot; a lib,   normally we would share 2 workspaces..   one for the lib it self, and another one for a sample workspace that demonstrates how it can/should be used.  <br />
<br />
Has DAW created any guide or how to approach in this sense to instruct us (the community)  on best way to start creating public server packages ? <br />
<br />
What would be the best approach ?   <br />
<br />
Create 2 independent packages ?  I think mingling the sample inside the main package seems messy,  as it won't be used at long term and it will definitely not be needed in most of target workspaces..   <br />
<br />
Any naming convention ?<br />
<br />
  Or keep the sample ws outside of packages scope, like in a public github only ? <br />
<br />
<br />
Regards</div>

]]></content:encoded>
			<category domain="https://support.dataaccess.com/Forums/forumdisplay.php?91-Studio-amp-Utilities"><![CDATA[Studio & Utilities]]></category>
			<dc:creator>Samuel Pizarro</dc:creator>
			<guid isPermaLink="true">https://support.dataaccess.com/Forums/showthread.php?73599-Package-Manager-(Lib-Sample)-approach</guid>
		</item>
	</channel>
</rss>
