[AccessD] Most common problems/situations

Excellent additions to my list of problems with development using Access as
the development/deployment vehicle. As opposed to "Bucket List", I'm
calling this my "Bitch List".

A.


On Wed, Aug 20, 2014 at 12:24 AM, Steve Schapel <
steve at datamanagementsolutions.biz> wrote:

> That's interesting, Jim.  I have never thought of the "automatic save of a
> main record when you move into a sub form control" as a problem.  Could you
> say a little more about how this causes pain?  Thanks.
>
> Regards
> Steve
>
>
> -----Original Message----- From: Jim Dettman
> Sent: Wednesday, August 20, 2014 1:03 PM
>
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Most common problems/situations
>
> Not sure what the goal is here, but I see these:
>
> 1. Inability to do a 3tier design.
> 2. VBA references/"runtime environment" as it's not a true .EXE.
> 3. Multiple versions of Office on the same PC.
> 4. Lack of 3rd party controls because Access does not fully implement the
> IDispatch interface.
> 5. Lack of control over the main Access window.
>
> as more of a pain because there's no real good solution for any of them
> expect #3 (sage) and still be an Access Developer.
>
> I suppose one thing beyond that which makes life really painful is the
> automatic save of a main record when you move into a sub form control.
>
> I'd have to say out of all the things taking Access "as is" and using it
> the way that it's was intended to be used, that one causes the most
> problems.
>
> Jim.
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
> Sent: Tuesday, August 19, 2014 12:08 PM
> To: Access Developers discussion and problem solving
> Subject: [AccessD] Most common problems/situations
>
> I'm trying to gather a list of the most common problems and situations
> faced by an Access developer (strictly referring to design/coding/form
> types/control types/classes, etc., and leaving aside problems such as
> time-and-billing, getting paid in a timely fashion, how to factor into your
> billing rate the depreciation on your hardware and software investments,
> etc.).
>
> The initial ones that come to mind are:
> - Input masks
> - Master/Detail forms (could be nested, as in
> Customers/Orders/OrderDetails)
> - Combo boxes (also involves Cascading Combos and NotInList behaviour)
> - List boxes (also involves NotInList behaviour)
> - Linked forms (a pair of forms; navigation on either causes navigation on
> the other)
> - Office Integration (links to Excel, Word, Outlook,etc.)
> - Custom Nav buttons (assuming you don't like those built-in)
> - On-the-fly creation of new forms/dialogs/reports
> - Search and Filter facilities
> - Reports scoped to either the current row, or criteria
> - API calls
> - Export current record/report to PDF and email same
> - (Advanced) Creation of custom classes, most commonly custom controls
>
> These are the common problems I have commonly faced and addressed. Do you
> have others to add to this list? Eagerly seeking addition to this list.
>
> --
> Arthur
> --
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>



-- 
Arthur