<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.45">
<TITLE>RE: [AccessD] AXP Question</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Along these lines there are several report creation/selection Access products out there. They are generally Forms and code you drop into the mdb. I know datacreations has one.</FONT></P>
<P><FONT SIZE=2>Jim Hale </FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Nancy Lytle [<A HREF="mailto:nancy.lytle@auatac.com">mailto:nancy.lytle@auatac.com</A>]</FONT>
<BR><FONT SIZE=2>Sent: Tuesday, June 10, 2003 2:20 PM</FONT>
<BR><FONT SIZE=2>To: accessd@databaseadvisors.com</FONT>
<BR><FONT SIZE=2>Subject: RE: [AccessD] AXP Question</FONT>
</P>
<BR>
<P><FONT SIZE=2>In a case like you mention, why not create a report frontend. Then use</FONT>
<BR><FONT SIZE=2>something like RFil5.0 (free) to allow for maximum variability in how they</FONT>
<BR><FONT SIZE=2>slice the data (you can even add some addition functionality of your own, to</FONT>
<BR><FONT SIZE=2>let them select fields to highlight, Create report titles, etc. Then save</FONT>
<BR><FONT SIZE=2>that information as a filter to the report.</FONT>
<BR><FONT SIZE=2>I have found that most database have a set number of often used information</FONT>
<BR><FONT SIZE=2>and then it is a matter of how that information is sliced.</FONT>
<BR><FONT SIZE=2>And having worked with end users in the legal and government as well as</FONT>
<BR><FONT SIZE=2>private sector, most users don't understand or want to understand that what</FONT>
<BR><FONT SIZE=2>may seem like a simple request, still takes time, especially if several</FONT>
<BR><FONT SIZE=2>people make "small requests".</FONT>
</P>
<P><FONT SIZE=2>HTH,</FONT>
<BR><FONT SIZE=2>Nancy L</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: accessd-bounces@databaseadvisors.com</FONT>
<BR><FONT SIZE=2>[<A HREF="mailto:accessd-bounces@databaseadvisors.com">mailto:accessd-bounces@databaseadvisors.com</A>]On Behalf Of Roz Clarke</FONT>
<BR><FONT SIZE=2>Sent: Monday, June 09, 2003 5:08 AM</FONT>
<BR><FONT SIZE=2>To: 'accessd@databaseadvisors.com'</FONT>
<BR><FONT SIZE=2>Subject: RE: [AccessD] AXP Question</FONT>
</P>
<BR>
<P><FONT SIZE=2>This makes perfect sense if writing an application that doesn't have to get</FONT>
<BR><FONT SIZE=2>changed by the users. But consider this scenario:</FONT>
</P>
<P><FONT SIZE=2>We are building a front end for a data warehousing application (data on SQL</FONT>
<BR><FONT SIZE=2>Server 7). We need the front end to be flexible as it must provide</FONT>
<BR><FONT SIZE=2>equivalent functionality to 4 Access databases currently in use, each</FONT>
<BR><FONT SIZE=2>holding anywhere from 4 - 40 forms and around 100 reports, which are updated</FONT>
<BR><FONT SIZE=2>& maintained solely by IT (a v. bad thing - we are committed to getting</FONT>
<BR><FONT SIZE=2>involved every time they want to change the layout of a report, and it</FONT>
<BR><FONT SIZE=2>causes an overnight delay as we can only write changes into the live</FONT>
<BR><FONT SIZE=2>database between 12 midnight and 6am. This has the users hopping mad and has</FONT>
<BR><FONT SIZE=2>resulted in the company failing to meet SLAs with client companies). We have</FONT>
<BR><FONT SIZE=2>been running AXP for 6 months and they have still not come to terms with the</FONT>
<BR><FONT SIZE=2>delays.</FONT>
</P>
<P><FONT SIZE=2>In A97 I would have made the forms & reports flexible by allowing users to</FONT>
<BR><FONT SIZE=2>a) make temporary changes to objects at runtime, replacing these at the end</FONT>
<BR><FONT SIZE=2>of the session, and b) copy report objects and make their own changes to the</FONT>
<BR><FONT SIZE=2>new report. Now I can't.</FONT>
</P>
<P><FONT SIZE=2>We can't provide each user with their own FE to hold even temporary changes</FONT>
<BR><FONT SIZE=2>as we are on terminal server.</FONT>
</P>
<P><FONT SIZE=2>I'm starting to think that Access has become the wrong tool for the job. Any</FONT>
<BR><FONT SIZE=2>suggestions?</FONT>
</P>
<P><FONT SIZE=2>Roz</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Wortz, Charles [<A HREF="mailto:CWortz@tea.state.tx.us">mailto:CWortz@tea.state.tx.us</A>]</FONT>
<BR><FONT SIZE=2>Sent: 06 June 2003 17:52</FONT>
<BR><FONT SIZE=2>To: accessd@databaseadvisors.com</FONT>
<BR><FONT SIZE=2>Subject: RE: [AccessD] AXP Question</FONT>
</P>
<BR>
<P><FONT SIZE=2>Brett,</FONT>
</P>
<P><FONT SIZE=2>You partition the app and have each developer work on their db. Then if the</FONT>
<BR><FONT SIZE=2>dbs need to be reunited you have a senior developer recombine them. You are</FONT>
<BR><FONT SIZE=2>using a configuration management and/or version control tool, are you not?</FONT>
</P>
<P><FONT SIZE=2>Charles Wortz</FONT>
<BR><FONT SIZE=2>Software Development Division</FONT>
<BR><FONT SIZE=2>Texas Education Agency</FONT>
<BR><FONT SIZE=2>1701 N. Congress Ave</FONT>
<BR><FONT SIZE=2>Austin, TX 78701-1494</FONT>
<BR><FONT SIZE=2>512-463-9493</FONT>
<BR><FONT SIZE=2>CWortz@tea.state.tx.us</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Brett Barabash [<A HREF="mailto:BBarabash@TappeConstruction.com">mailto:BBarabash@TappeConstruction.com</A>]</FONT>
<BR><FONT SIZE=2>Sent: Friday 2003 Jun 06 11:10</FONT>
<BR><FONT SIZE=2>To: 'accessd@databaseadvisors.com'</FONT>
<BR><FONT SIZE=2>Subject: RE: [AccessD] AXP Question</FONT>
</P>
<P><FONT SIZE=2>What about environments like ours where you have multiple developers</FONT>
<BR><FONT SIZE=2>developing in the same development MDB? It was fairly trivial to do this</FONT>
<BR><FONT SIZE=2>with older versions of Access.</FONT>
</P>
<BR>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Wortz, Charles [<A HREF="mailto:CWortz@tea.state.tx.us">mailto:CWortz@tea.state.tx.us</A>]</FONT>
<BR><FONT SIZE=2>Sent: Friday, June 06, 2003 11:00 AM</FONT>
<BR><FONT SIZE=2>To: accessd@databaseadvisors.com</FONT>
<BR><FONT SIZE=2>Subject: RE: [AccessD] AXP Question</FONT>
</P>
<BR>
<P><FONT SIZE=2>As I said in another post, since the dark ages of computing, professional</FONT>
<BR><FONT SIZE=2>developers have a development version of the application they work on, and</FONT>
<BR><FONT SIZE=2>the users use a production version of the application. When you are ready to</FONT>
<BR><FONT SIZE=2>move the development version to production, you follow a set procedure to</FONT>
<BR><FONT SIZE=2>replace the old production version with the new production version. Only in</FONT>
<BR><FONT SIZE=2>dire emergencies should a developer have to tinker with the actual</FONT>
<BR><FONT SIZE=2>production version. And even then, all the users should be out of the</FONT>
<BR><FONT SIZE=2>application.</FONT>
</P>
<P><FONT SIZE=2>All the above applies whether the application is in Access, VB, Cobol,</FONT>
<BR><FONT SIZE=2>SQLServer, VFP, Oracle, etc. I doubt that you can find any software</FONT>
<BR><FONT SIZE=2>development shop that has been in business for a few years that doesn't</FONT>
<BR><FONT SIZE=2>follow this model. If you have been developing software for a while, I am</FONT>
<BR><FONT SIZE=2>sure you follow this model (at least informally) just to keep your sanity.</FONT>
</P>
<P><FONT SIZE=2>Charles Wortz</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Charlotte Foust [<A HREF="mailto:cfoust@infostatsystems.com">mailto:cfoust@infostatsystems.com</A>]</FONT>
<BR><FONT SIZE=2>Sent: Friday 2003 Jun 06 10:45</FONT>
<BR><FONT SIZE=2>To: accessd@databaseadvisors.com</FONT>
<BR><FONT SIZE=2>Subject: RE: [AccessD] AXP Question</FONT>
</P>
<P><FONT SIZE=2>Not unwanted by everyone. I'm perfectly happy with that change.</FONT>
</P>
<P><FONT SIZE=2>Charlotte Foust</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: ACTEBS [<A HREF="mailto:actebs@actebs.com.au">mailto:actebs@actebs.com.au</A>]</FONT>
<BR><FONT SIZE=2>Sent: Friday, June 06, 2003 7:24 AM</FONT>
<BR><FONT SIZE=2>To: accessd@databaseadvisors.com</FONT>
<BR><FONT SIZE=2>Subject: RE: [AccessD] AXP Question</FONT>
</P>
<BR>
<P><FONT SIZE=2>Terri,</FONT>
</P>
<P><FONT SIZE=2>Charles just alerted me to the fact that since the release of A2K, if you</FONT>
<BR><FONT SIZE=2>use the Shift key to bypass the normal startup, you are opening the DB</FONT>
<BR><FONT SIZE=2>exclusively. A new unwanted feature kindly supplied by M$...</FONT>
</P>
<P><FONT SIZE=2>Vlad</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: accessd-bounces@databaseadvisors.com</FONT>
<BR><FONT SIZE=2>[<A HREF="mailto:accessd-bounces@databaseadvisors.com">mailto:accessd-bounces@databaseadvisors.com</A>] On Behalf Of Terri Jarus</FONT>
<BR><FONT SIZE=2>Sent: Friday, 6 June 2003 10:27 PM</FONT>
<BR><FONT SIZE=2>To: accessd@databaseadvisors.com</FONT>
<BR><FONT SIZE=2>Subject: [AccessD] AXP Question</FONT>
</P>
<BR>
<P><FONT SIZE=2>I have upgraded a FE database from A97 to AXP successfully, however, a</FONT>
<BR><FONT SIZE=2>major difference that is annoying me is the fact that in a multiuser</FONT>
<BR><FONT SIZE=2>environment, I am unable to make changes to the design unless I open</FONT>
<BR><FONT SIZE=2>exclusively.</FONT>
</P>
<P><FONT SIZE=2>I never had this problem in A97 and now that my users are all getting</FONT>
<BR><FONT SIZE=2>upgraded to the AXP FE, I am running across a few areas that need to be</FONT>
<BR><FONT SIZE=2>tweaked and can't do it until everyone is out of the db. This is a shared</FONT>
<BR><FONT SIZE=2>network FE.</FONT>
</P>
<P><FONT SIZE=2>I should probably give everyone their own copy on their desktop, however,</FONT>
<BR><FONT SIZE=2>this database has evolved greatly over the past 3 years and has required</FONT>
<BR><FONT SIZE=2>many changes. I have always been able to make these changes while the db</FONT>
<BR><FONT SIZE=2>was being used by others with no problem. There are about 20 users - so</FONT>
<BR><FONT SIZE=2>upgrading everyone's FE would be very tedious.</FONT>
</P>
<P><FONT SIZE=2>I know there are some automated programs to do the updating, but one I had</FONT>
<BR><FONT SIZE=2>tried took too long and was cumbersome to the user.</FONT>
</P>
<P><FONT SIZE=2>Any suggestions or ideas - is there a setting I'm missing that would allow</FONT>
<BR><FONT SIZE=2>design changes while in use???</FONT>
</P>
<P><FONT SIZE=2>Thanks for any help. _______________________________________________</FONT>
<BR><FONT SIZE=2>AccessD mailing list</FONT>
<BR><FONT SIZE=2>AccessD@databaseadvisors.com</FONT>
<BR><FONT SIZE=2><A HREF="http://databaseadvisors.com/mailman/listinfo/accessd" TARGET="_blank">http://databaseadvisors.com/mailman/listinfo/accessd</A></FONT>
<BR><FONT SIZE=2>Website: <A HREF="http://www.databaseadvisors.com" TARGET="_blank">http://www.databaseadvisors.com</A></FONT>
<BR><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>AccessD mailing list</FONT>
<BR><FONT SIZE=2>AccessD@databaseadvisors.com</FONT>
<BR><FONT SIZE=2><A HREF="http://databaseadvisors.com/mailman/listinfo/accessd" TARGET="_blank">http://databaseadvisors.com/mailman/listinfo/accessd</A></FONT>
<BR><FONT SIZE=2>Website: <A HREF="http://www.databaseadvisors.com" TARGET="_blank">http://www.databaseadvisors.com</A></FONT>
</P>
<P><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>AccessD mailing list</FONT>
<BR><FONT SIZE=2>AccessD@databaseadvisors.com</FONT>
<BR><FONT SIZE=2><A HREF="http://databaseadvisors.com/mailman/listinfo/accessd" TARGET="_blank">http://databaseadvisors.com/mailman/listinfo/accessd</A></FONT>
<BR><FONT SIZE=2>Website: <A HREF="http://www.databaseadvisors.com" TARGET="_blank">http://www.databaseadvisors.com</A></FONT>
</P>
</BODY>
</HTML>