[AccessD] New Database Table - How to Proceed - Azure?

We're using it at work.

Well, at least the place that I'll be working at for the next week (I start
a new job next week).

We used ADP's very heavily here and with the release of Office 2013, they
have dropped support for ADPs.

We are in the process of moving all of our relational DBs up to SQL Azure
and our transactional DBs up to NoSQL.

Our front ends are moving to OOP style programming using HTML5, C#, Web
services, Javascript (Knockout, Jquery).

There really is no major difference for us when dealing with Azure, since
we were using web services to talk to SQL.

I'm not sure how hard it would be if you are planning on staying with
Access as a FE for your SQL db.

I don't know much about the pricing structure, but believe it is a few
dollars a month.

David

On Tue, Mar 25, 2014 at 8:36 AM, Brad Marks <BradM at blackforestltd.com>wrote:

> All,
>
> Thanks to everyone who posted their ideas and insights.  I appreciate it.
>
> I am curious if anyone has worked with Windows Azure SQL Database.
> I have briefly looked at this approach and I am curious if it would be a
> good approach for a small firm.
>
> Thanks,
> Brad
>
>
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com on behalf of Gary Kjos
> Sent: Tue 3/25/2014 8:36 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] New Database Table - How to Proceed
>
> I think that people who haven't actually used Access often have a bias
> against it. The "risk" of an Access DB would be possibly a corruption issue
> that couldn't be recovered from excepting reverting to a previous backup.
> With the amount of updates that would seem to not be a huge risk for your
> application. Assuming that these updates could be reentered somehow and are
> not being captured ONLY in the database without other documentation.
>
> If I were in your place, I would be using an Access backend at least to
> develop it. I would plan on having backups made at minimum every day with a
> rotating cycle of daily/weekly/monthly backups so that if some catastrophic
> issue was encountered you could go back generations if necessary as
> sometimes there could be an undetected error with something that you don't
> even realize there is a problem with.
>
> Sql Server Express would be my upgrade plan or where the final version
> would reside once the development in Access was complete or near to it.
> During development you are likely to be fiddling with additional fields and
> perhaps more tables etc. A single table?  Really?  Is that a well thought
> out design?  And making those changes in the tool you are most familiar
> with will speed your development.  On the other hand that would also be a
> good opportunity to learn the procedures to do this in SQL Server too.
>
> Is this a publicly held company?  If you are subject to audits using Access
> for a business critical application might be looked at suspiciously where
> SQL Server, even the Express version would be better accepted by outside
> auditors.
>
> Good luck!
>
> GK
>
>
> On Mon, Mar 24, 2014 at 4:15 PM, Brad Marks <BradM at blackforestltd.com
> >wrote:
>
> > All,
> >
> > I have a question, but first I need to explain a little background.
> >
> >
> --
> Gary Kjos
> garykjos at gmail.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> This message was scanned by ESVA and is believed to be clean.
> Click here to report this message as spam.
> http://h0stname/cgi-bin/learn-msg.cgi?id=9CDE32864E.1C65F
>
>
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>