Re: really basic access question
- From: Tom van Stiphout <no.spam.tom7744@xxxxxxx>
- Date: Thu, 31 Jan 2008 07:15:14 -0700
On Thu, 31 Jan 2008 03:01:12 -0800 (PST), wildman@xxxxxxxxxxxx wrote:
See comments inline.
-Tom.
It's been over 10 years that I don't look at Access. I've been workingAccess or the Access runtime need to be on every client. So does the
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?
front-end application.
An MDB can be compiled into an MDE to remove the code. Other objects
How does one limit what the client can see? For example, will the
client be able to unlink tables, view code, etc?
such as the database window can be hidden.
Yes, but there are a few differences so a thorough test is in order.
Will a 2003 ap usually run under Access 2007?
Yes, It's VBA - Visual Basic for Applications.
I noticed they've included code with the application. It looks like
vb6, is it?
.
Thanks for any help or information.
- References:
- really basic access question
- From: wildman
- really basic access question
- Prev by Date: preventing users to import data from another mdb file
- Next by Date: XPDL integration into Access Application?
- Previous by thread: really basic access question
- Next by thread: Re: really basic access question
- Index(es):