StrataFrame Forum

Importation of Date type column with DDT 1.t.6

http://forum.strataframe.net/Topic31588.aspx

By Michel Levy - 11/18/2012

Hi,
  • Source table in VFP, with a field of Date type produces a DateTime column in DDT
  • Source table in SQL Server with a column of Date type produces an Int column in DDT
Deployment is OK, Date is deployed as Date.

Workaround is easy (modifying the structure in DDT), but please, could you provide a patch for this, or may we have to wait for 2.0 ?

Kind Regards

[Edit : topic should be ... DDT 1.7.6, sorry for the typo]
By Trent L. Taylor - 11/18/2012

Michel:
  • Native versioning which allows you to build and get back to any version of your database at any time.  This also allows you to keep working on a new build while still building an older version of your software.
  • 100% deployment support for SQL Server as well as (in time) My SQL.  We are planning to provide support for multiple database platforms.
  • The DDT will have execution templates for integration into SSMS (SQL Server Management Studio) so that you can store execution parms for a certain sproc, then have it build the execution for you and run inside of the DDT or be exported to work inside of the SSMS.  This allows you to have infinite test scenarios for any SPROC.  Very handy.
  • External SQL file support for automated updates back into the DDT.  Some people like to work externally in SSMS in SQL files then copy those files back into the DDT.  We will have an automatic "synchronization" of these files back into the DDT.
  • A true IDE development environment.  The environment will be one of the nicest changes.  It will be an environment more akin to Visual Studio allowing multiple tables and sprocs to be worked on at the same time.
  • Improved searching.  You will be able to search anything, including fields, object history, etc.
  • Robust enough to now allow true database admins to use on a daily basis and accommodate all of their IT needs.
  • Fully WPF.  All new environments like this will be in WPF and all that is entailed, including cleaner and smoother interfaces, notification animations, pretty themes, etc. 
But back to your original inquiry, I will look at the current VFP import.  We will still be supporting a VFP import, so I will make sure that this gets corrected.
By Edhy Rijo - 11/18/2012

Trent L. Taylor (11/18/2012)
Michel:
  • Fully WPF.  All new environments like this will be in WPF and all that is entailed, including cleaner and smoother interfaces, notification animations, pretty themes, etc. 

So does this mean, that we will be able to create WPF and XAML applications with SF?
By Trent L. Taylor - 11/18/2012

Absolutely!  That is the entire purpose.  You will be able to natively bind to any WPF control, list, grid, etc. with the new SF BOs that are entity based.  We will also be releasing a WPF control collection.  We will have the following control collections:

  1. WPF Control Suite
  2. WinForms Control Suite
  3. ASP.NET Control Suite
  4. Silverlight Control Suite
  5. And maybe....Compact Framework Control Suite
We are keeping the compact framework in mind from the beginning this go around so that the framework will support virtually any .NET platform you want to develop applications for.
By Edhy Rijo - 11/18/2012

Trent,

This is BIG!!!!!, AWESOME!!!! BigGrin

I have been struggling around with other non .net tool to be able to deliver fast web application and wishing to have XAML support in SF.  Now the question is when we will be able to see something workable?
By Michel Levy - 11/18/2012

WOW!!!!!!

w00t

nothing else than THANKS
By Eric Leissler - 11/18/2012

the problem  is not only with foxpro import

it s same on sql import

look at this video

 
 


Have you a solution for this problem ?

Thanks

best regard


 
By Olivier - 11/18/2012

Trent L. Taylor (11/18/2012)
Absolutely!  That is the entire purpose.  You will be able to natively bind to any WPF control, list, grid, etc. with the new SF BOs that are entity based.  We will also be releasing a WPF control collection.  We will have the following control collections:

  1. WPF Control Suite
  2. WinForms Control Suite
  3. ASP.NET Control Suite
  4. Silverlight Control Suite
  5. And maybe....Compact Framework Control Suite
We are keeping the compact framework in mind from the beginning this go around so that the framework will support virtually any .NET platform you want to develop applications for.


If the SF are based on Entity, plus our method, we are the happiest developers !

Thanks Trent !
By Trent L. Taylor - 11/19/2012

Now the question is when we will be able to see something workable?                           


Well, for some of our existing customers, like yourselves, we will probably offer a beta program that will allow you to get your hands on it sooner than the rest of the market.  We have just increased our work week by 10-15 hours a week that is dedicated solely on SF.  So even though I don't have an exact date for you, we are working hard on it.  We need these tools for ourselves also.  The only thing that is slowing us down, is the 1st quarter requirements that we have for our medical suite.  There is another bout of government regulations coming, but the good news is that we already have most if it taken care of and our new SF development schedule will not be impacted.

Once we get a little further, we will start posting things out here on the forum for you to start looking at and making any suggestions (i.e. did we miss a feature, etc.).

If the SF are based on Entity, plus our method, we are the happiest developers !


That is exactly what we want to hear!!! Smile
By Edhy Rijo - 11/19/2012

Thanks Trent Smile
By Trent L. Taylor - 11/19/2012

Eric:

I took the sample you sent me via PM and debugged this and it is now fixed.  I will post another build in the next few days.  If you have a need for this today, let me know and I will do a side build and send it over to you.