newbie question - local queries

  • Thread starter Thread starter larpup
  • Start date Start date
L

larpup

I've been asked to re-write an access app with sql backend.. can anyone
enlighten me regarding "how to emulate Access local queries"? Since
sql server is all on the backend, how does one make unique views for a
workstation?

Any advice is appreciated.

Lar
 
why would you need unique views for a particular workstation?

more appropriately; you can do this for a particular user.

but it's all hogwash.

why would susies' view be different than toms?

seriously; in great detail

do you know how to program?

local queries, local tables-- they're completely unnecessary and all
they do is make your application too complex.

-Aaron
 
Response as follows:

why would you need unique views for a particular workstation?
Click to expand...
I have never used SQL Server, but have started reading and studying it.

I work in Access and a legacy program which permits queries to the
local workstation.
more appropriately; you can do this for a particular user.

but it's all hogwash.

why would susies' view be different than toms?
Click to expand...

I understand a vew is a "RETUN" of a query. So two or more workstations
can execute the same sql or store procedure at same time then? As I
said, am inexperienced with SQL Server.
seriously; in great detail > do you know how to program?
Click to expand...
I am inexperienced to SQL Server and attempting to educate myself. If
you are so experienced , then it would behoove you to have a better
attitude. It could possibly you business, but that's another matter.
local queries, local tables-- they're completely unnecessary and all
they do is make your application too complex.
Click to expand...
Not interested in local tables. Need to educate myself on the
differences between Access and SQL Server.
 
thanks but I dont have a problem getting business

for the most part, 2 people can run the same query at the same time--
unless you use some wierd persistent tables instead of using
tempTables.

Select *
INTO #SysObjects
From Sysobjects
Click to expand...

this builds a temp table.. if you have 2 people that need to do the
same stuff at the same time; they will each have their own connection
so they can both fire this exact same statement

Select *
INTO #SysObjects
From Sysobjects
Click to expand...
 
and for the record... when Paul Revere was riding through town; he
didn't sit there and say 'why pardon me, the redcoats are coming'

he pulled through tiown; screaming at the top of his lungs..

when 80% of the people that use Access are effectively CRACK ADDICTS
for using MDB; then I have _NO_PROBLEM_ ruffling a few feathers.

Over the years; I've run into too many MDB developers that have 10
years experience that make $15/hour-- I mean; it's a travesty... these
people sit here and slave away on MDB.. just spinning their wheels.

take that MDB knowledge; build SQL Server solutions (with Access Data
Projects); and presto-chango-- you're making $80k.

-Aaron
 
Thanks for the advice. I was hoping that identifying myself as a
newbie would pretty much give the idea, that, I am a NEWBIE... I do
appreciate the advice very much.

Regards,

Lar
 
Back
Top