Access 2007 and Visual Studio 2008

  • Thread starter Thread starter Jorge Ribeiro
  • Start date Start date
J

Jorge Ribeiro

Hello

I've been asking to write a small Acess 2007 departamental application.
My App will be on a remote file server and users will operate using links to
the specific folder. My client doesn't have web servers nor will install them
or other kind of server, like SQL Server (so, web app are out!).

To build a pure Access 2007 application it seems that i'm stucked with VBA
as visual studio 2008 does not support Access in new VSTO tools for Office
System.

Is this right?! Does Visual Studio 2008 lacks the ability to provide a way
of building enhanced Access 2007 applications, as it does to Word or Excel?!
An Access 2007 developper still has to dive into VBA to have things done?

Please end my long search and answer this brief questions...

Best regards

Jorge
 
Yes, you must use VBA (or macros) in an Access database.

You can, of course, develop a .Net application that gets its data from the
Jet database, but you wouldn't be developing in Access in that case, you'd
be developing in Visual Studio.
 
On Fri, 14 Nov 2008 03:37:03 -0800, Jorge Ribeiro

Access applications are developed in the Access environment, using
VBA.
I am concerned about your "remote file server". How remote? It needs
to be on the LAN, or on a VERY STABLE dedicated VPN connection. The
public internet does not count.
OTOH you say "departmental", so the backend can be on the departmental
file server on the LAN.
If you are asked to write "a small A2007 application", why are you
considering a web app or SQL Server? That seems to be outside of the
requirements.

-Tom.
Microsoft Access MVP
 
Tom & Douglas thanx for the replies

We proposed a solution that involved Infopath forms (for latter integration
with Sharepoint) and Web services for posting those forms data to a database
made with SQL Server.

The client said that, because of a lacking backup policy, such servers (IIS
and SQL
Server) where not be considered critical so, in cause of failure, those
services would only be restored over a period that could be measured in days.
However the target of this new solution is a very critical team of my
client's business so that's a major setback.

The only systems available that are in fact assured of a quick failover
recovery are file system (not so remote sorry... in same LAN) and Email.
We will make this using a central Access db on server and client app's with
linked tables.

Because we are already VS2008 followers (and .Net failtfull belivers!) we
thouth that the new Office System provided some upgrade to Access apps as it
already does for other office apps (Excel, Word)

Now i'm secure that it ain't so... thanx again

We now know what's the best path to follow... and the only one!

best regards

Jorge
 
Jorge good night

I am Rubens Caxilé from Brasil.

Your better solution is use TS Terminal Server and develop your application
normaly in MS Access, the only consideration that you have to do is create
foldens for each remote users to store the mdes files.
 
Back
Top