![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
On May 4, 6:35*pm, "Albert D. Kallal" <PleaseNOOOsPAMmkal... (AT) msn (DOT) com wrote: "James A. Fortune" *wrote in messagenews:21819a07-8c68-47d7-8a30-938fde64cce4 (AT) l6g2000vbn (DOT) googlegroups.com... If LightSwitch starts out with managed code, then its logical extension would be a jump to VS, not Access. Access 2010 tried to keep the same two hats while putting on a third! That is, it tried to add the third hat of becoming a RAD tool for the web. In terms of access having support for sharepoint or now office 365, I think we have a far better play in this regards. All be the first to admit that it with access web services, having to adopt sharepoint is too high a price for the average access developer market. However I'm playing with office 365 right now, and the results are really wonderful. And with a small business package, it looks like we're gonnasee some really reasonable cost numbers. I'm always interested in reasonable cost numbers. *Keep us posted. What I'd like to see is a converter that takes an Access database connected to SQL Server and creates a VS project with three tiers and all the underlying managed code necessary to output the reports into either a PDF file or a WPF format. *That would be RAD :-). *Then Access could do what it does best. Well first of all the last two versions of access does have native reprots to PDF and does so without a pdf printer driver. So PDF support is now built into Access. Hopefully, everyone knows that PDF output is possible from Access. I'd need PDF output from the hypothetical 'Access converted into VS project'. In fact the really issue or thing that I think as an Access community will run into with regards to Access web development is the need for that easy plug in extensibility to the web development environment that we've always had on the desktop. To me this is the challenge, but also the key to the future of access web version services. However with the announcement of office 365, and the fact that it'll support access web services, we've at least now crossed one bridge that will result in an easy and widespread affordability for access web publishing. For web sites that really impress, I'm really liking the JQuery capabilities that got added into VS. *It's very exciting. *I don't see Access yet as a RAD web tool, but I'll certainly be taking a close look at its web capabilities. *Maybe MS will add JQuery to Access' web tools in a future version? James A. Fortune CDMAPos... (AT) FortuneJames (DOT) com |
#12
| |||
| |||
|
|
*<aaron.ke... (AT) gmail (DOT) com> wrote *> Access / Jet sucks balls old man. It is *> IMPOSSIBLE to make Jet perform *> well in a multi-user environment. (1) Whether it does or not, Mr. Kempf, you are dodging the issue. *You claimed that LightSwitch is a "new version of Access", which it is not, thus giving Yet Another Example of your not knowing whereof you speak. (2) Within their size, number of users, and network limitations (all of which are well-known for years), Access and Jet have, indeed, performed well in multiuser environments. *Anyone who would deem it "worthless" simply because it is not (and is/was not intended to be) an enterprise level database and UI combination is, at best, a dunderhead. On May 2, 4:09 pm, "Access Developer" <accde... (AT) gmail (DOT) com> wrote: Mr. Kempf, I just wonder why you feel so compelled to denigrate Access that you misrepresent facts, time after time. FYI, the answer to the title of the article reference is "No, LightSwitch isn't the 'new Access'." Microsoft has never represented it as such, much less as a "new versionof Access". -- Larry Linson, Microsoft Office Access MVP Co-author: "Microsoft Access Small Business Solutions", published by Wiley Access newsgroup support is alive and well in USENET comp.databases.ms-access aaron.ke... (AT) gmail (DOT) com> wrote http://visualstudiomagazine.com/arti...vb_using-light.... |
![]() |
| Thread Tools | |
| Display Modes | |
| |