Re: Sybase to Access

Tech-Archive recommends: Fix windows errors by optimizing your registry

No, they usually compact it in the middle of the night.

Try not to be unnecessarily abusive, Aaron. You don't comprehend
why the solution was chosen, and I'm not going to explain it to you,
because all you'll do is whine about VB going away.

Robin S.
VB2005.Net programmer
----------------------------------
<aaron.kempf@xxxxxxxxx> wrote in message
news:1167887286.837763.116380@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
rofl

you fucking retards still kick users out of the databases in order to
compact and repair?

how fucking antiquated

I mean seriously your little bull*** dime-store solutions aren't
trouble free.

they just send their work elsewhere since you're a fucking newbie
Access baby mother fucker

-Aaron



RobinS wrote:
Well, it doesn't matter to me whether or not you believe me. The
application is still running 2 years after I left, and the database
is now about 900MB. Their only complaint is how long it takes to
compact it...

Robin S.
--------------------------------------------------
<aaron.kempf@xxxxxxxxx> wrote in message
news:1167866804.486388.155330@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I disagree.

I don't know or care how much effort it took; all I know is that
ADP
is
a better platform.

MDB is for lamers and fucking retards.

it makes no sense for newbies to learn TWO DIFFERENT DIALECTS OF
SQL.

That is the FATAL FLAW WITH MDB-- It shouldn't be targeted at
Junior
Developers.
And it's not reliable enough for normal developers.

I just don't believe you when you say that you've had 75 users and
500mb data.

I've had a dozen MDB files with a total of 1.5 gb crap out left and
right.
and I've had a single MDB split properly into front end and back
end
(gag) that can't support a half dozen users.

-Aaron


RobinS wrote:
Bummer for you. I've had VB desktop applications using Access as a
back-end that had 75 users and 500MB+ of data, with no problem
whatsoever. There's no reason that wouldn't work for sstory, if he
didn't want to use SQLServer.

Robin S.
----------------------------------
<aaron.kempf@xxxxxxxxx> wrote in message
news:1167768642.603440.102460@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I've had Access apps with 25 mb of data that can't support a
half
dozen
users.

MDB shouldn't be used for a single user nor a single record.

If MS had a decade-long policy of preaching SQL over MDB then
_MAYBE_
I
would be willing to accept SQL 2005 _CRAP_ that is built into VB
2005.

As it is; I can't reccomend SQL 2005 _anywhere_ since it's not
supported on TRANSMETA (_BLADES_ and tablets), it doesn't
support
SQL
Agent; and it doesn't support replication like MSDE 2.0 did

-Aaron


RobinS wrote:
Why would Access bite with a 30MB database -- that's nothing.
I've had apps with an Access database that was 500MB, and the
performance was fine.

It would be better to migrate to SQLServer Express, but using
Access won't kill him.

Robin S.
---------------------------------
"sstory" <nothank@xxxxxx> wrote in message
news:uLrM4NpLHHA.4848@xxxxxxxxxxxxxxxxxxxxxxx
Not sure of the question.

1.) Access would really bite with a 30MB database--not
recommended.
2.) Access could use link tables to link to Sybase perhaps
and
give
you "access" to it. then again, why would you use Access if
that
were
possible instead of just getting the drivers to connect
directly
to
Sybase.
3.) If it is a problem you might consider migrating to
MySQL.
"codercode" <wong.jamin@xxxxxxxxx> wrote in message
news:1166120551.784318.13300@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I'm working on a Visual Basic .NET using Access database.
However,
my
client already have a 30MB database with Sybase ASA and
Sybase
is
way
too much for that. Is there anyway I can migrate from a
Sybase
to
Access? or is it possible at all. If it is not, can these
two
databases
co-exist together?








.

Quantcast