PDA

View Full Version : (Wish List) Expand and Collaps source code



Takashi Arikuma
12-Nov-2005, 10:09 AM
Wish the ability to expand and collaps the source code like Visual Studio.

This is usefull when writting large codes. Collaps and expands on:

Procedure - End_Procedure
Function - End_Function
If xxx Begin - End If
and others...

Regards,

Takashi

Hendrik van Niekerk
12-Nov-2005, 03:36 PM
very good idea! I like that
U need to submit it...

Hendrik van Niekerk
"Takashi Arikuma" <takashi.arikuma@bizworktech.com> wrote in message
news:riadHr55FHA.2708@dacmail.dataaccess.com...
> Wish the ability to expand and collaps the source code like Visual Studio.
>
> This is usefull when writting large codes. Collaps and expands on:
>
> Procedure - End_Procedure
> Function - End_Function
> If xxx Begin - End If
> and others...
>
> Regards,
>
> Takashi
>
>
>

Dennis Piccioni
14-Nov-2005, 09:52 AM
On Sat, 12 Nov 2005 11:09:00 -0400, "Takashi Arikuma"
<takashi.arikuma@bizworktech.com> wrote:

>Wish the ability to expand and collaps the source code like Visual Studio.
>
>This is usefull when writting large codes. Collaps and expands on:
>
>Procedure - End_Procedure
>Function - End_Function
>If xxx Begin - End If
>and others...
>
>Regards,
>
>Takashi
>
>
Hi Takashi,

I know that this is already on the list of changes for the Next
Generation Studio for Visual DataFlex that is in development now. I
don't know if code collapse will make the first release of the Studio,
scheduled for VDF 12.0, but it is on our list already.

Regards,
Dennis

Dennis Piccioni
Data Access Worldwide
http://www.DataAccess.com/support

Torkild U. Resheim
16-Nov-2005, 04:48 PM
Takashi Arikuma wrote:

> Wish the ability to expand and collaps the source code like Visual Studio.
>
> This is usefull when writting large codes. Collaps and expands on:
>
> Procedure - End_Procedure
> Function - End_Function
> If xxx Begin - End If
> and others...
>
> Regards,
>
> Takashi
I guess you mean something like this:
http://resheim.no/vdf/documentation/manual/2-4-editor.html ;-)

Regards,
Torkild

wila
17-Nov-2005, 02:49 AM
Torkild U. Resheim wrote:
> I guess you mean something like this:
> http://resheim.no/vdf/documentation/manual/2-4-editor.html ;-)

Nice ... :)

--
Wil

>
> Regards,
> Torkild

Torkild U. Resheim
17-Nov-2005, 03:02 AM
Wil van Antwerpen wrote:

> Torkild U. Resheim wrote:
>> I guess you mean something like this:
>> http://resheim.no/vdf/documentation/manual/2-4-editor.html ;-)
>
> Nice ... :)
>
> --
> Wil
>
>>
>> Regards,
>> Torkild
Thanks Wil :-)

Regards,
Torkild.

Dave &/or Wempy
17-Nov-2005, 09:03 AM
I've had a stay-at-home year, no DISD, no Miami conference or
MMISL(toe?) for me; so I've no idea what prompted the big push on
Studio 2.

Was this really top of the wish list? I haven't seen the howls of
horror that accompanied the announcement of Winprint2 so I assume the
Studio2 concept is popular?

Having said that, did DAW consider repackaging Eclipse? The more I see
of both Eclipse and of Torkild's work on it the more impressed I
become.

Weekend in South Beach coming up, woot!

Dave


On Mon, 14 Nov 2005 09:52:40 -0500, Dennis Piccioni
<dennis@dataaccess.com> wrote:

>On Sat, 12 Nov 2005 11:09:00 -0400, "Takashi Arikuma"
><takashi.arikuma@bizworktech.com> wrote:
>
>>Wish the ability to expand and collaps the source code like Visual Studio.
>>
>>This is usefull when writting large codes. Collaps and expands on:
>>
>>Procedure - End_Procedure
>>Function - End_Function
>>If xxx Begin - End If
>>and others...
>>
>>Regards,
>>
>>Takashi
>>
>>
>Hi Takashi,
>
>I know that this is already on the list of changes for the Next
>Generation Studio for Visual DataFlex that is in development now. I
>don't know if code collapse will make the first release of the Studio,
>scheduled for VDF 12.0, but it is on our list already.
>
>Regards,
>Dennis
>
>Dennis Piccioni
>Data Access Worldwide
>http://www.DataAccess.com/support

Marco
17-Nov-2005, 08:38 PM
Dave,

I can only speak for the Miami conference;
I believe that this one was not as such requested by the developer-base,
but by DAW Product development, as it solves a lot of current issues.

Although I was sceptical at first (another change that the end-user (our
bread) does not see or feel). But it does make sense in the productivity
way, so I guess we can either charge more, or do more things we like.

Problems 'solved' would be like:
- Compiler errors no longer require source editor to be moved to full
source code
- Better debugging integration, so that breakpoints can be set while in
the studio
- When 'typing' a visual object, it automatically gets rendered in the
visual designer panel
- All properties will be visible in the source code, not just the ones
that are not in the properties window.
- No more // studio markers, that confuse developers
- Probably a lot and a lot more I forget

I think that this is indeed necessary for making VDF a product that
attracts new developers. And where developers used to MS Studio are
happy to work with. So in the bigger picture of getting more market
share, this definitely fits in my opinion.

I also believe that Torkild has a fantastic product (eclipse plugin)
that every developer should at least have a look at.

Cheers,
Marco


Dave &/or Wempy wrote:
> I've had a stay-at-home year, no DISD, no Miami conference or
> MMISL(toe?) for me; so I've no idea what prompted the big push on
> Studio 2.
>
> Was this really top of the wish list? I haven't seen the howls of
> horror that accompanied the announcement of Winprint2 so I assume the
> Studio2 concept is popular?
>
> Having said that, did DAW consider repackaging Eclipse? The more I see
> of both Eclipse and of Torkild's work on it the more impressed I
> become.
>
> Weekend in South Beach coming up, woot!
>
> Dave
>
>
> On Mon, 14 Nov 2005 09:52:40 -0500, Dennis Piccioni
> <dennis@dataaccess.com> wrote:
>
>
>>On Sat, 12 Nov 2005 11:09:00 -0400, "Takashi Arikuma"
>><takashi.arikuma@bizworktech.com> wrote:
>>
>>
>>>Wish the ability to expand and collaps the source code like Visual Studio.
>>>
>>>This is usefull when writting large codes. Collaps and expands on:
>>>
>>>Procedure - End_Procedure
>>>Function - End_Function
>>>If xxx Begin - End If
>>>and others...
>>>
>>>Regards,
>>>
>>>Takashi
>>>
>>>
>>
>>Hi Takashi,
>>
>>I know that this is already on the list of changes for the Next
>>Generation Studio for Visual DataFlex that is in development now. I
>>don't know if code collapse will make the first release of the Studio,
>>scheduled for VDF 12.0, but it is on our list already.
>>
>>Regards,
>>Dennis
>>
>>Dennis Piccioni
>>Data Access Worldwide
>>http://www.DataAccess.com/support

Archie Campbell
18-Nov-2005, 11:43 AM
Coincidently, yesterday I was looking at JasperReports.
A design product called JasperAssistant runs with Eclipse (i think)

I suppose the advantage of Eclipse is that one product can act as the IDE
for various development products:
. VDF
. JasperAssistant
. Java
. etc ...

Yeah?

Hmmm Interesting
Archie




"Torkild U. Resheim" <torkildr@resheim.no> wrote in message
news:QkOsx006FHA.2168@dacmail.dataaccess.com...
> Wil van Antwerpen wrote:
>
> > Torkild U. Resheim wrote:
> >> I guess you mean something like this:
> >> http://resheim.no/vdf/documentation/manual/2-4-editor.html ;-)
> >
> > Nice ... :)
> >
> > --
> > Wil
> >
> >>
> >> Regards,
> >> Torkild
> Thanks Wil :-)
>
> Regards,
> Torkild.

Archie Campbell
18-Nov-2005, 11:56 AM
Hi Torkild

I am reading your manual (nice manual btw) and I feel I need an answer to
the following question:

Why would I want to develop VDF Windows and Web Apps using Eclipse instead
of the Studio?


Thanks
Archie

"Torkild U. Resheim" <torkildr@resheim.no> wrote in message
news:QkOsx006FHA.2168@dacmail.dataaccess.com...
> Wil van Antwerpen wrote:
>
> > Torkild U. Resheim wrote:
> >> I guess you mean something like this:
> >> http://resheim.no/vdf/documentation/manual/2-4-editor.html ;-)
> >
> > Nice ... :)
> >
> > --
> > Wil
> >
> >>
> >> Regards,
> >> Torkild
> Thanks Wil :-)
>
> Regards,
> Torkild.

Hendrik van Niekerk
18-Nov-2005, 04:03 PM
Again (as I have said this before) maybe someone out there could bring this
and demo it at the next DISD in Feb. We are looking for people to show/demo
new stuff. It might even be a great topic for the Thursday before the
conference.

Hendrik van Niekerk

"Marco Kuipers" <marco.kuipers@nci.com.au> wrote in message
news:Cjz1bD%236FHA.3660@dacmail.dataaccess.com...
> Dave,
>
> I can only speak for the Miami conference;
> I believe that this one was not as such requested by the developer-base,
> but by DAW Product development, as it solves a lot of current issues.
>
> Although I was sceptical at first (another change that the end-user (our
> bread) does not see or feel). But it does make sense in the productivity
> way, so I guess we can either charge more, or do more things we like.
>
> Problems 'solved' would be like:
> - Compiler errors no longer require source editor to be moved to full
> source code
> - Better debugging integration, so that breakpoints can be set while in
> the studio
> - When 'typing' a visual object, it automatically gets rendered in the
> visual designer panel
> - All properties will be visible in the source code, not just the ones
> that are not in the properties window.
> - No more // studio markers, that confuse developers
> - Probably a lot and a lot more I forget
>
> I think that this is indeed necessary for making VDF a product that
> attracts new developers. And where developers used to MS Studio are happy
> to work with. So in the bigger picture of getting more market share, this
> definitely fits in my opinion.
>
> I also believe that Torkild has a fantastic product (eclipse plugin) that
> every developer should at least have a look at.
>
> Cheers,
> Marco
>
>
> Dave &/or Wempy wrote:
>> I've had a stay-at-home year, no DISD, no Miami conference or
>> MMISL(toe?) for me; so I've no idea what prompted the big push on
>> Studio 2. Was this really top of the wish list? I haven't seen the
>> howls of
>> horror that accompanied the announcement of Winprint2 so I assume the
>> Studio2 concept is popular?
>>
>> Having said that, did DAW consider repackaging Eclipse? The more I see
>> of both Eclipse and of Torkild's work on it the more impressed I
>> become.
>>
>> Weekend in South Beach coming up, woot!
>>
>> Dave
>>
>>
>> On Mon, 14 Nov 2005 09:52:40 -0500, Dennis Piccioni
>> <dennis@dataaccess.com> wrote:
>>
>>
>>>On Sat, 12 Nov 2005 11:09:00 -0400, "Takashi Arikuma"
>>><takashi.arikuma@bizworktech.com> wrote:
>>>
>>>
>>>>Wish the ability to expand and collaps the source code like Visual
>>>>Studio.
>>>>
>>>>This is usefull when writting large codes. Collaps and expands on:
>>>>
>>>>Procedure - End_Procedure
>>>>Function - End_Function
>>>>If xxx Begin - End If
>>>>and others...
>>>>
>>>>Regards,
>>>>
>>>>Takashi
>>>>
>>>>
>>>
>>>Hi Takashi,
>>>
>>>I know that this is already on the list of changes for the Next
>>>Generation Studio for Visual DataFlex that is in development now. I
>>>don't know if code collapse will make the first release of the Studio,
>>>scheduled for VDF 12.0, but it is on our list already.
>>>
>>>Regards,
>>>Dennis
>>>
>>>Dennis Piccioni
>>>Data Access Worldwide
>>>http://www.DataAccess.com/support

Torkild U. Resheim
18-Nov-2005, 04:11 PM
Archie Campbell wrote:

> Hi Torkild
>
> I am reading your manual (nice manual btw) and I feel I need an answer to
Thanks :-) It's a beginning.
> the following question:
>
> Why would I want to develop VDF Windows and Web Apps using Eclipse instead
> of the Studio?
Why would you want to write C apps in EMACS instead of vi ;-) Actually, the
Eclipse VDF plugins are a supplement to the VDF Studio. The product is
designed to help maintain large codebases. Something that I feel is very
much neglected by VDF Studio. I normally use Eclipse for class
library/datadictionary stuff and the VDF Studio for GUI and views in
general.
Even if you don't have a large codebase I think many of the features in the
plugin will be helpful to most VDF programmers. Ie. warnings about code
problems, content assist (IntelliType in M$ terms I think), code tooltips,
clean configurable interface, CVS support, and so on. The docs only mention
a fragment of the features available, most of which are standard Eclipse.
Another benefit is (as you mentioned in another posting) the number of other
plugins for Eclipse and the open API. This means that if you don't find a
plugin supporting what you need (pretty unlikely these days), you can write
your own.

Btw: The plugin does not yet support VDF WebApp development "out of the
box". It can be done using other plugins in addition to the VDF plugins.

[snip]

Regards,
Torkild

Archie Campbell
18-Nov-2005, 08:15 PM
Thanks for the reply Torkild

Hopefully I will get a chance to try it this weekend.

Archie



"Torkild U. Resheim" <torkildr@resheim.no> wrote in message
news:86wKqSI7FHA.3660@dacmail.dataaccess.com...
> Archie Campbell wrote:
>
> > Hi Torkild
> >
> > I am reading your manual (nice manual btw) and I feel I need an answer
to
> Thanks :-) It's a beginning.
> > the following question:
> >
> > Why would I want to develop VDF Windows and Web Apps using Eclipse
instead
> > of the Studio?
> Why would you want to write C apps in EMACS instead of vi ;-) Actually,
the
> Eclipse VDF plugins are a supplement to the VDF Studio. The product is
> designed to help maintain large codebases. Something that I feel is very
> much neglected by VDF Studio. I normally use Eclipse for class
> library/datadictionary stuff and the VDF Studio for GUI and views in
> general.
> Even if you don't have a large codebase I think many of the features in
the
> plugin will be helpful to most VDF programmers. Ie. warnings about code
> problems, content assist (IntelliType in M$ terms I think), code tooltips,
> clean configurable interface, CVS support, and so on. The docs only
mention
> a fragment of the features available, most of which are standard Eclipse.
> Another benefit is (as you mentioned in another posting) the number of
other
> plugins for Eclipse and the open API. This means that if you don't find a
> plugin supporting what you need (pretty unlikely these days), you can
write
> your own.
>
> Btw: The plugin does not yet support VDF WebApp development "out of the
> box". It can be done using other plugins in addition to the VDF plugins.
>
> [snip]
>
> Regards,
> Torkild

Torkild U. Resheim
19-Nov-2005, 04:53 AM
Archie Campbell wrote:

> Thanks for the reply Torkild
No problem :-)
>
> Hopefully I will get a chance to try it this weekend.
Good luck! If you need any assistance you can direct your questions to the
mailing list and I'll try to respond ASAP. Things are a bit hectic here as
my number of children recently increased by 200%, so I may be quite slow
responding.
I should also mention that the support for struct arrays is limited in the
version that is out. Much better support is being implemented and I hope to
release the 0.5.20 version within a week.

Regards,
Torkild
>
> Archie
>
>
>
> "Torkild U. Resheim" <torkildr@resheim.no> wrote in message
> news:86wKqSI7FHA.3660@dacmail.dataaccess.com...
>> Archie Campbell wrote:
>>
>> > Hi Torkild
>> >
>> > I am reading your manual (nice manual btw) and I feel I need an answer
> to
>> Thanks :-) It's a beginning.
>> > the following question:
>> >
>> > Why would I want to develop VDF Windows and Web Apps using Eclipse
> instead
>> > of the Studio?
>> Why would you want to write C apps in EMACS instead of vi ;-) Actually,
> the
>> Eclipse VDF plugins are a supplement to the VDF Studio. The product is
>> designed to help maintain large codebases. Something that I feel is very
>> much neglected by VDF Studio. I normally use Eclipse for class
>> library/datadictionary stuff and the VDF Studio for GUI and views in
>> general.
>> Even if you don't have a large codebase I think many of the features in
> the
>> plugin will be helpful to most VDF programmers. Ie. warnings about code
>> problems, content assist (IntelliType in M$ terms I think), code
>> tooltips, clean configurable interface, CVS support, and so on. The docs
>> only
> mention
>> a fragment of the features available, most of which are standard Eclipse.
>> Another benefit is (as you mentioned in another posting) the number of
> other
>> plugins for Eclipse and the open API. This means that if you don't find a
>> plugin supporting what you need (pretty unlikely these days), you can
> write
>> your own.
>>
>> Btw: The plugin does not yet support VDF WebApp development "out of the
>> box". It can be done using other plugins in addition to the VDF plugins.
>>
>> [snip]
>>
>> Regards,
>> Torkild

Marco
20-Nov-2005, 06:13 PM
Hendrik,

I have thought about this, and briefly mentioned this to Torkild.

I was not ready for a commitment yet, though... I guess you can slot me
in for a presentation on the Eclipse Plugin...

Cheers,
Marco


Hendrik van Niekerk wrote:
> Again (as I have said this before) maybe someone out there could bring this
> and demo it at the next DISD in Feb. We are looking for people to show/demo
> new stuff. It might even be a great topic for the Thursday before the
> conference.
>
> Hendrik van Niekerk
>
> "Marco Kuipers" <marco.kuipers@nci.com.au> wrote in message
> news:Cjz1bD%236FHA.3660@dacmail.dataaccess.com...
>
>>Dave,
>>
>>I can only speak for the Miami conference;
>>I believe that this one was not as such requested by the developer-base,
>>but by DAW Product development, as it solves a lot of current issues.
>>
>>Although I was sceptical at first (another change that the end-user (our
>>bread) does not see or feel). But it does make sense in the productivity
>>way, so I guess we can either charge more, or do more things we like.
>>
>>Problems 'solved' would be like:
>>- Compiler errors no longer require source editor to be moved to full
>>source code
>>- Better debugging integration, so that breakpoints can be set while in
>>the studio
>>- When 'typing' a visual object, it automatically gets rendered in the
>>visual designer panel
>>- All properties will be visible in the source code, not just the ones
>>that are not in the properties window.
>>- No more // studio markers, that confuse developers
>>- Probably a lot and a lot more I forget
>>
>>I think that this is indeed necessary for making VDF a product that
>>attracts new developers. And where developers used to MS Studio are happy
>>to work with. So in the bigger picture of getting more market share, this
>>definitely fits in my opinion.
>>
>>I also believe that Torkild has a fantastic product (eclipse plugin) that
>>every developer should at least have a look at.
>>
>>Cheers,
>>Marco
>>
>>
>>Dave &/or Wempy wrote:
>>
>>>I've had a stay-at-home year, no DISD, no Miami conference or
>>>MMISL(toe?) for me; so I've no idea what prompted the big push on
>>>Studio 2. Was this really top of the wish list? I haven't seen the
>>>howls of
>>>horror that accompanied the announcement of Winprint2 so I assume the
>>>Studio2 concept is popular?
>>>
>>>Having said that, did DAW consider repackaging Eclipse? The more I see
>>>of both Eclipse and of Torkild's work on it the more impressed I
>>>become.
>>>
>>>Weekend in South Beach coming up, woot!
>>>
>>>Dave
>>>
>>>
>>>On Mon, 14 Nov 2005 09:52:40 -0500, Dennis Piccioni
>>><dennis@dataaccess.com> wrote:
>>>
>>>
>>>
>>>>On Sat, 12 Nov 2005 11:09:00 -0400, "Takashi Arikuma"
>>>><takashi.arikuma@bizworktech.com> wrote:
>>>>
>>>>
>>>>
>>>>>Wish the ability to expand and collaps the source code like Visual
>>>>>Studio.
>>>>>
>>>>>This is usefull when writting large codes. Collaps and expands on:
>>>>>
>>>>>Procedure - End_Procedure
>>>>>Function - End_Function
>>>>>If xxx Begin - End If
>>>>>and others...
>>>>>
>>>>>Regards,
>>>>>
>>>>>Takashi
>>>>>
>>>>>
>>>>
>>>>Hi Takashi,
>>>>
>>>>I know that this is already on the list of changes for the Next
>>>>Generation Studio for Visual DataFlex that is in development now. I
>>>>don't know if code collapse will make the first release of the Studio,
>>>>scheduled for VDF 12.0, but it is on our list already.
>>>>
>>>>Regards,
>>>>Dennis
>>>>
>>>>Dennis Piccioni
>>>>Data Access Worldwide
>>>>http://www.DataAccess.com/support
>
>
>

Torkild U. Resheim
20-Nov-2005, 06:33 PM
Marco Kuipers wrote:

> Hendrik,
>
> I have thought about this, and briefly mentioned this to Torkild.
>
> I was not ready for a commitment yet, though... I guess you can slot me
> in for a presentation on the Eclipse Plugin...
Cool :-) I'd be happy to provide you with any input you need.
>
> Cheers,
> Marco
>
>
[snip]
Regards,
Torkild.

Garret Mott
20-Nov-2005, 06:55 PM
If I can make it this year, I'd love to see a presentation on Eclipse! OK,
I'd like to see it anyway, but I'm thinking Torkild has better things to do
than visit Vermont <g>.

Thanks,

Garret

"Hendrik van Niekerk" <hendrik@mchsi.com> wrote in message
news:bNFQtPI7FHA.3660@dacmail.dataaccess.com...
> Again (as I have said this before) maybe someone out there could bring
> this and demo it at the next DISD in Feb. We are looking for people to
> show/demo new stuff. It might even be a great topic for the Thursday
> before the conference.
>
> Hendrik van Niekerk
>
> "Marco Kuipers" <marco.kuipers@nci.com.au> wrote in message
> news:Cjz1bD%236FHA.3660@dacmail.dataaccess.com...
>> Dave,
>>
>> I can only speak for the Miami conference;
>> I believe that this one was not as such requested by the developer-base,
>> but by DAW Product development, as it solves a lot of current issues.
>>
>> Although I was sceptical at first (another change that the end-user (our
>> bread) does not see or feel). But it does make sense in the productivity
>> way, so I guess we can either charge more, or do more things we like.
>>
>> Problems 'solved' would be like:
>> - Compiler errors no longer require source editor to be moved to full
>> source code
>> - Better debugging integration, so that breakpoints can be set while in
>> the studio
>> - When 'typing' a visual object, it automatically gets rendered in the
>> visual designer panel
>> - All properties will be visible in the source code, not just the ones
>> that are not in the properties window.
>> - No more // studio markers, that confuse developers
>> - Probably a lot and a lot more I forget
>>
>> I think that this is indeed necessary for making VDF a product that
>> attracts new developers. And where developers used to MS Studio are happy
>> to work with. So in the bigger picture of getting more market share, this
>> definitely fits in my opinion.
>>
>> I also believe that Torkild has a fantastic product (eclipse plugin) that
>> every developer should at least have a look at.
>>
>> Cheers,
>> Marco
>>
>>
>> Dave &/or Wempy wrote:
>>> I've had a stay-at-home year, no DISD, no Miami conference or
>>> MMISL(toe?) for me; so I've no idea what prompted the big push on
>>> Studio 2. Was this really top of the wish list? I haven't seen the
>>> howls of
>>> horror that accompanied the announcement of Winprint2 so I assume the
>>> Studio2 concept is popular?
>>>
>>> Having said that, did DAW consider repackaging Eclipse? The more I see
>>> of both Eclipse and of Torkild's work on it the more impressed I
>>> become.
>>>
>>> Weekend in South Beach coming up, woot!
>>>
>>> Dave
>>>
>>>
>>> On Mon, 14 Nov 2005 09:52:40 -0500, Dennis Piccioni
>>> <dennis@dataaccess.com> wrote:
>>>
>>>
>>>>On Sat, 12 Nov 2005 11:09:00 -0400, "Takashi Arikuma"
>>>><takashi.arikuma@bizworktech.com> wrote:
>>>>
>>>>
>>>>>Wish the ability to expand and collaps the source code like Visual
>>>>>Studio.
>>>>>
>>>>>This is usefull when writting large codes. Collaps and expands on:
>>>>>
>>>>>Procedure - End_Procedure
>>>>>Function - End_Function
>>>>>If xxx Begin - End If
>>>>>and others...
>>>>>
>>>>>Regards,
>>>>>
>>>>>Takashi
>>>>>
>>>>>
>>>>
>>>>Hi Takashi,
>>>>
>>>>I know that this is already on the list of changes for the Next
>>>>Generation Studio for Visual DataFlex that is in development now. I
>>>>don't know if code collapse will make the first release of the Studio,
>>>>scheduled for VDF 12.0, but it is on our list already.
>>>>
>>>>Regards,
>>>>Dennis
>>>>
>>>>Dennis Piccioni
>>>>Data Access Worldwide
>>>>http://www.DataAccess.com/support
>
>