By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,165 Members | 840 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,165 IT Pros & Developers. It's quick & easy.

really basic access question

P: n/a
It's been over 10 years that I don't look at Access. I've been working
in asp.net for the last 5 developing intranet sites.

Just got a project where we are trying to avoid building an
application by virtue of reusing something already in place at another
site developed in Access 2003.

I've never seen the application in production, apparently access2003
linked to SQL server 2005 db.

My really basic questions,

presuming the application will only run on a single station, what's
the best way to deploy? Does access still need to run on every client?

How does one limit what the client can see? For example, will the
client be able to unlink tables, view code, etc?

Will a 2003 ap usually run under Access 2007?

I noticed they've included code with the application. It looks like
vb6, is it?

Thanks for any help or information.

Jan 31 '08 #1
Share this Question
Share on Google+
1 Reply


P: n/a
On Jan 31, 5:01*am, wild...@noclient.net wrote:
...
My really basic questions,

presuming the application will only run on a single station, what's
the best way to deploy? Does access still need to run on every client?
Essentially, yes, having each user run the applicaiton using their own
copy of Access is the simplest thing to do.
However, it is possible to create a runtime application which permits
the user to run only your app w/o having to have Access. I find that
Access is pretty ubiquitous in most professional environments, so it's
not much of an issue.

Here's the link to the '07 SDK
http://www.microsoft.com/downloads/d...displaylang=en
>
How does one limit what the client can see? For example, will the
client be able to unlink tables, view code, etc?
There are a number of options to limit what the user can do from
making the app so easy that they'll never look behind the scenes to
hiding the database window at startup to out and out locking down the
applicaiton. I recommend searching the archive for specific questions
and choosing the solution that makes the most sense for you and the
evnvironment.
>
Will a 2003 ap usually run under Access 2007?
Yes, if it was well written it will run without modification. There
may be some issues w/ the DAO references and the like, but they're
relatively easy to fix.
>
I noticed they've included code with the application. It looks like
vb6, is it?
VBA - a derivitive of VB. Dialect might be a better word.
>
Thanks for any help or information.
Good luck.

Tim Mills-Groninger
Jan 31 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.