[AccessD] Back End Updater modifications

Hi Fred
Glad you like BEU but sounds like you've done a lot of extra stuff. We have
talked about further versions but it's finding the time. One thing Reuben
did recently was add the functionality to run a query rather than just
embedded SQL, so you might find that useful. I've added a couple of
facilities I needed too, namely allowing a function to be specified as the
default value on a field (eg today's date), and I've added a Print facility
which prints the changes between 2 version numbers, which I've found useful.
If you want any of that I can send it off-list.

So, lots of scope for improvements, and yours sound great, esp the changing
field types one. If you wanted to share any of that I'm sure we'd be
interested.

-- Andy Lacey
http://www.minstersystems.co.uk 

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com 
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Fred Hooper
> Sent: 19 November 2005 02:17
> To: 'Access Developers discussion and problem solving'
> Subject: [AccessD] Back End Updater modifications
> 
> 
> I've been using this intensively for the past few months and 
> I'd like to thank the writers for their fine program; it's 
> saved me many hours of work.
> 
> While I think I've read references here to other versions, 
> I've only found Version 1 so perhaps the items below are 
> redundant with newer versions.
> 
> While using the Back End Updater I've needed to make a few 
> changes and extensions and I'm hoping that there's a process 
> for checking them and making them available to others; e.g. a 
> new version.
> 
> The changes/extensions are:
> 
> (1)  Dropped tables - When used with older back ends where 
> the tables still existed in the back end, the updater 
> couldn't use those dropped tables, for instance in SQL 
> statements for earlier updates. I added code that checked for 
> tables to be dropped and added links if the tables existed at 
> the start of the updating process.
> 
> (2)  SQL statements - 255 characters wasn't enough so I added 
> some fields & code to bring it up to 1020 characters.
> 
> (3)  Connection strings to back end - These are different for 
> A2000; I modified them so they work for A97 - A2003.
> 
> (4)  Password-protected back ends - I've put one on the back 
> end to keep browsers out (the password is the app's name, so 
> it's not serious). However, I needed to modify the code to support it.
> 
> (5)  Changing field types - I found some code on the internet
> (http://aislebyaisle.com/access/vba_backend_code.htm) that 
> supported this. With minor changes I've made it work for me. 
> I'm hopeful that the author, Allen Beechick, will make it 
> available to us (although I haven't contacted him).
> 
> (6)  Running code - Some changes just *needed* code. Rather 
> than writing such code outside the BE Updater, I extended it 
> to running a function as one of the main options.
> 
> Fred Hooper
> 
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com 
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>