RealBasic for an Access Front End?

[Dave]

I work at a small private company that has been using VB 6.0 as a
front end for Access databases for 8 years. It looks as though we
will be migrating to Vista in the not-too-distant future. My hope is
to move to RealBasic at that point. Does anyone know about RB
connecting to Access tables via ADO? I was reading some archived RB
posts and someone wrote that RB doesn't connect to Access. That was
from a 2004 post. Is that (still) correct? Seems kind of strange
for a company that is marketing itself as the answer to the VB6 or
VB.NET upgrade question.

Your insight will be appreciated.

Dave

[Larry Linson]

"Dave" <da*****@msn.co mwrote

PS: Even if I *do* retire early, I will always remember
this group as a great source for friendly help for this
self-taught programmer (I just have a business degree!)

Many of us, at best, can only claim to be "semi-retired." When a "bluebird
lands on our shoulder," it's hard to convince ourselves we should "shoo it
away." <CHUCKLE>

[David W. Fenton]

"Larry Linson" <bo*****@localh ost.notwrote in
news:3h%yi.1549 5$4K6.9988@trnd dc02:

With the emphasis on ACCDBs (direct descendant of MDB and Jet) in
Access 2007, I think that Microsoft got the message that not
everybody's going to go for a server DB backend -- as it once it
appeared. Access 2007, though, has not, in fact, abandoned MDB
and Jet; those are still an option. But I'd be less concerned
about the longevity of MDBs or MDB-like Access databases.

You'd think that, but there are some things going on that tell you
they don't take Access/Jet seriously.

1. dropping ULS in the new format and replacing it with a database
password.

2. dropping replication in the new format in favor of SharePoint.

3. dropping support for heterogeneous replication between Jet and
SQL Server with SQL Server 2005.

Sense a pattern there?

I certainly do, and it's that Jet is for desktop applications, and
as soon as you need a server or security or multiple locations, then
you should use one of MS's other server products. That is, if you
need security and the db password isn't good enough, or you need
replication and SharePoint isn't good enough, you have to switch to
SQL Server 2005.

So, they are doing the same thing, pushing their server products,
but instead of just denigrating.dep racating Jet as they did starting
with Access 2000, they are removing the functionality from the new
data format so that you're forced to use SQL Server.

At least, that's the way it looks to me.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[David W. Fenton]

Dave <da*****@msn.co mwrote in
news:11******** **************@ i13g2000prf.goo glegroups.com:

before I would take them
any further forward with VB6-Access

I think you show a surprising degree of ignorance when you use
"Access" in this context. YOU ARE NOT USING ACCESS. You are only
usingn Jet. You may use Access to create your MDBs, but that's the
end of Access's involvement in your application.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Dave]

On Aug 22, 6:46 pm, "David W. Fenton" <XXXuse...@dfen ton.com.invalid >
wrote:

Dave <[e-mail] mwrote innews:11****** *************** *@i13g2000prf.g ooglegroups.com :

before I would take them
any further forward with VB6-Access

I think you show a surprising degree of ignorance when you use
"Access" in this context.

Never claimed to be a highly experienced code jockey, just feeding my
family.