what the **** you talking about asshole
homedude-- the arrogant sql guy-- was saying 'access knowledge wont
help you with oracle'
and im saying he's full of shit
access is the first database anyone SHOULD learn.
they should use it for about a week lol.
I just want to know what the **** this david portas jack ass is saying
you're discouraging this mdb-kiddie from learning a real database
and i just want to know who the **** you think that you are david.
Of course we should be encouraging MDB-kiddies to be learning a real
database.
Microsoft has proven time, and time again their lack of dedication to
the RDBMS market-- if they gave a shit then they would take it
seriously.
i have a list of 10 bugs in access.
when Microsoft stops fucking around and starts fixing bugs-- is when
it's ok for these kids to keep on using MDB.
as it is; microsoft is too proud and drunk on their own success to
remain competitive.
so yeah-- go ahead kid; learn Oracle.
experiment with Oracle.
right-click link, files of type = 'odbc' and make a friggin ton of
linked tables to oracle.
most importantly you need to write SQL Passthrough queries; because MDB
sucks balls you've got to write all your queries on the server side.
start a new query, view, sql view-- query tab, special query types; i
wish i remembered the verbage-- sql passthrough.
under the edit menu select properties; maybe you can just right click..
the 2nd or 3rd argument down is 'odbc connection string'.
i personally prefer SPT to linked tables for everything-- because you
can do a simple copy and paste of the odbc connection string property..
in linked tables; it's a big old pain in the ass because it's a read
only property.. so if you want to set it as a custom string; you need
to do it programmatically
yes; go ahead bud-- screw around with the oracle side. see if you can
make updates; but try updates on the base tables; not updates against
views or access-side joins.