Forum Replies Created

Viewing 15 posts - 46 through 60 (of 67 total)

  • RE: Writing Nearly Codeless Apps: Part 2

    GregFrazer (10/13/2010)


    It is not true to say that:

    "Unfortunately in this day & age we still don't have relational databases that allow us to divide our various objects into different...

  • RE: Writing Nearly Codeless Apps: Part 2

    Really? Do you have any stats/research that backs up that assertion? I'm not an expert on what developers do but I have extensive experience as a DBA and...

  • RE: Writing Nearly Codeless Apps: Part 2

    richardd (10/13/2010)


    [quote-0If that's the case then your database design sucks. If there's a table called "Customers", why would there ever be a view called "Customers" in the same schema? It's...

  • RE: Writing Nearly Codeless Apps: Part 2

    roger.plowman (10/13/2010)


    Ok, I have a problem with the approach from the word go, and it's this:

    "implement "ideal" auditing, where the app itself can recall all versions of the data that...

  • RE: Writing Nearly Codeless Apps: Part 2

    Grant Fritchey (10/13/2010)


    Oh please no, not tables named TBxxx. That's just so 1992 (not to mention, very, very Access). Surely, at this point in history, we can simply name a...

  • RE: Writing Nearly Codeless Apps: Part 1

    Ed Salva (10/8/2010)


    I'm enjoying reading the comments, but I'm curious, what happens when someone comes up with a better engine (or as in our case better software)?

    Do we...

  • RE: Writing Nearly Codeless Apps: Part 1

    RonKyle (10/7/2010)


    RAP is in the same spirit. The objective is to properly and systematically do what most programmers currently do both imporperly and inconsistently. They do these things poorly because...

  • RE: Writing Nearly Codeless Apps: Part 1

    gbaytler (10/7/2010)


    Column in the application is defined as 'DATE', which is not available as a datatype in SQL Server 2005. It is introduced in SQL Server 2008.

    The article text...

  • RE: Writing Nearly Codeless Apps: Part 1

    eric.cardinal (10/7/2010)


    At the end of the article it kind of sums it up for me where you are going with this...Henry Ford's craftsman didn't like the assembly line approach either....

  • RE: Writing Nearly Codeless Apps: Part 1

    gbaytler (10/7/2010)


    Column in the application is defined as 'DATE', which is not available as a datatype in SQL Server 2005. It is introduced in SQL Server 2008.

    The article text...

  • RE: Writing Nearly Codeless Apps: Part 1

    Ahmed Saad (10/7/2010)


    I am also developing an application with similar goal as that of RAP but with a different approach. It is UI driven, which means all the back-end stuff...

  • RE: Writing Nearly Codeless Apps: Part 1

    timothyawiseman (10/6/2010)


    I think it makes sense to decide, if not table by table, then certainly database by database whether you want to use artificial keys. I find the idea of...

  • RE: Writing Nearly Codeless Apps: Part 1

    Roger L Reid (10/6/2010)


    Another silver bullet for "what's wrong with software development".

    The rhetoric is familiar:

    1. Assert such a problem exists - "every knows it", so no analysis needed

    2. Make a...

  • RE: Writing Nearly Codeless Apps: Part 1

    C. Grant Anderson (10/6/2010)


    A lot of talk about relative points and yes it does really look like a promotional ad. After skimming the website and related white paper the...

  • RE: Writing Nearly Codeless Apps: Part 1

    bienvenunet (10/6/2010)


    Question: Can RAP and the concepts that the series will discuss be used to develop Web Parts and features for SharePoint?

    I have no experience with coding SharePoint and so...

Viewing 15 posts - 46 through 60 (of 67 total)