DataBase - Access 2007 and Visual Studio 2008
Asked By JorgeRibeir
14-Nov-08 06:37 AM
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
SQL Server
(1)
Visual Studio 2008
(1)
Office System
(1)
Access 2007
(1)
Excel
(1)
Word
(1)
VSTO
(1)
VBA
(1)
Douglas J. Steele replied...
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.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
Tom van Stiphout replied...
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
JorgeRibeir replied...
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
RubensCaxi replied...
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.
Roger Jennings on Access / Sharepoint DataBase http: / / www.quepublishing.com / articles / article.aspx?p = 1606238 I was very dismayed this article, is it makes it pretty clear that in-house hosting of your Sharepoint server with Access Services to support browser-based Access apps is something only large companies will be able to afford, because the pricing and licensing for the Enterprise version is very, very steep. The alternative is hosted Sharepoint / Access Services, and the costs do not seem terribly high. It seems to me that the pricing is upside-down. Big enterprises do not want to deploy Access apps in the browser - - they will build their own .NET apps, browser-based or not 2010 does not really save them money (because of the 64-bit requirements of Sharepoint Server 2010, it could vastly increase those costs for organizations with legacy hardware). The features of Access 2010 used in conjunction with Sharepoint 2010 seem to me to be most compelling for
Might be outgrowing Access but daunted by SQL Server DataBase I am close to completing the consolidation of various small Access databases and a couple of Excel spreadsheets that my little company uses (5 staff) into an all encompasing Access database and I was planning on splitting the database when I was finished to allow simaltaneous use of it by staff on our small office network. However it is becoming more and more obvious to me that I am going to need to give staff access to this new database from remote locations (outside of our office network). Two staff members
SQL query slow DataBase Hi In the code below I found that it takes 1.3 seconds to load. There is a possible reason, it reads from a local MDB file (access), and it reads from some 270000 rows (result some 15-20 rows, where the highest are counted 150000, 50000, 40000, 26000, remaining are 100's). This is probably more Access that Visual Studio, though - is there a way to split it up or cancel the query? And can I read this faster? string sql = EquipmentID(Equipment) + StartDate.ToOADate().ToString(FloatFormat, myCulture) + EndDate.ToOADate().ToString(FloatFormat, myCulture); sql + = " group by event_id, name"; _Log("Calc thread #2"); OleDbCommand com = new OleDbCommand sql, con); _Log("Calc thread #3"); From #2 to #3 it takes 1.3 seconds. Remaing
Access for the Macintosh? DataBase Will this application be ported over to the Mac in the and be able to defend the faith, CERM is your place. http: / / www.cerm.info Access Discussions SQL Server (1) MySQL (1) Visual Studio (1) Outlook (1) Office (1) Excel (1) Word (1) MDAC (1) While we are not privy to all of the decisions