Sunday, February 19, 2012

.adp successor front-end to SQL Server 2005

If rumours are true that .adp is likely to be phased out in future MS Access
versions, what front-end with similar functionality (forms, reports, coding)
would you suggest for development and use with MS SQL Server?Personally, I use VB.Net for everything but reporting. It gives you a lot
of flexibility, and automates many tasks (sometimes too much).
For reporting, you can use a thrid party reporting product like Crystal, or
try out SQL Server Reporting Services. I hate Crystal, and haven't really
worked much with SQL Server Reporting Services, but you can check out
newgroups for either and see what folks have to say about the benefits and
limitations of each.
"Lolik" <Lolik@.discussions.microsoft.com> wrote in message
news:817CD550-356C-4FD5-8D2B-BFE6E22379D1@.microsoft.com...
> If rumours are true that .adp is likely to be phased out in future MS
Access
> versions, what front-end with similar functionality (forms, reports,
coding)
> would you suggest for development and use with MS SQL Server?|||Jim, many thanks for replying.
Is VB 2005 the newer version of VB.Net, or a different branch of VB
altogether?
Which would be easier to learn to achieve .adp similar functionality?
"Jim Underwood" wrote:

> Personally, I use VB.Net for everything but reporting. It gives you a lot
> of flexibility, and automates many tasks (sometimes too much).
> For reporting, you can use a thrid party reporting product like Crystal, o
r
> try out SQL Server Reporting Services. I hate Crystal, and haven't really
> worked much with SQL Server Reporting Services, but you can check out
> newgroups for either and see what folks have to say about the benefits and
> limitations of each.
> "Lolik" <Lolik@.discussions.microsoft.com> wrote in message
> news:817CD550-356C-4FD5-8D2B-BFE6E22379D1@.microsoft.com...
> Access
> coding)
>
>|||2005 is just the latest version of .Net. If your company is already using
.Net I would see what version they are on and go with that. If not, then I
would go with the newest version. Either one is going to be more
programming focused than what you are used to, but I don't think either
version will be any easier or more difficult. A good book on programming in
.Net will be helpful.
"Lolik" <Lolik@.discussions.microsoft.com> wrote in message
news:64F18985-1925-42ED-A212-33273A5EE7CC@.microsoft.com...
> Jim, many thanks for replying.
> Is VB 2005 the newer version of VB.Net, or a different branch of VB
> altogether?
> Which would be easier to learn to achieve .adp similar functionality?
>
> "Jim Underwood" wrote:
>
lot
or
really
and|||Thanks Jim..
"Jim Underwood" wrote:

> 2005 is just the latest version of .Net. If your company is already using
> ..Net I would see what version they are on and go with that. If not, then
I
> would go with the newest version. Either one is going to be more
> programming focused than what you are used to, but I don't think either
> version will be any easier or more difficult. A good book on programming
in
> ..Net will be helpful.
> "Lolik" <Lolik@.discussions.microsoft.com> wrote in message
> news:64F18985-1925-42ED-A212-33273A5EE7CC@.microsoft.com...
> lot
> or
> really
> and
>
>

No comments:

Post a Comment