A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » General Discussion
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Update databases



 
 
Thread Tools Display Modes
  #1  
Old June 30th, 2009, 12:47 PM posted to microsoft.public.access
NevilleT
external usenet poster
 
Posts: 159
Default Update databases

Before I spend time developing something, does anyone know of a tool or code
I can use to automatically update an MDE to a new version. Basically do a
compare of objects and import new ones from a file. Want to be able to send
to clients and let them run it so I can bring them up to the latest version.

Would also be interested in anyone who has experience of doing an online
check for new versions of an Access database. Google did not throw up
anything of interest.
  #2  
Old June 30th, 2009, 03:59 PM posted to microsoft.public.access
John W. Vinson
external usenet poster
 
Posts: 18,261
Default Update databases

On Tue, 30 Jun 2009 04:47:01 -0700, NevilleT
wrote:

Before I spend time developing something, does anyone know of a tool or code
I can use to automatically update an MDE to a new version. Basically do a
compare of objects and import new ones from a file. Want to be able to send
to clients and let them run it so I can bring them up to the latest version.

Would also be interested in anyone who has experience of doing an online
check for new versions of an Access database. Google did not throw up
anything of interest.


You should absolutely use a split database, with the tables in one shared
"backend" database and the forms, reports, queries etc. in a separate
frontend, with links to the tables. This is essential in a multiuser database,
but in your situation it's a good idea too. When you have a new form or
report, the user can simply delete their frontend (there's no data in it after
all!) and replace it with the new one.

Tony Toews has an automated frontend update which will simplify this process;
see http://www.granite.ab.ca/access and look at his Tips and Best Practices
links.

--

John W. Vinson [MVP]
  #3  
Old July 1st, 2009, 06:21 AM posted to microsoft.public.access
NevilleT
external usenet poster
 
Posts: 159
Default Update databases

Thanks John. I have a split database. Was looking to possibly do a couple
of things.
- When the program is opened, check a web site to see if updates available.
Maybe use an ftp download of a text file to check version number???
- Download an update if necessary.
- Check MSysObjects DateUpdate to see if objects need to be replaced.
- Delete objects and import new objects from the downloaded files.

Will check out the database on Tony's site. Maybe I am being too ambitious
but it would be a nice little utility to handle updates.

Neville Turbit
www.projectperfect.com.au

"John W. Vinson" wrote:

On Tue, 30 Jun 2009 04:47:01 -0700, NevilleT
wrote:

Before I spend time developing something, does anyone know of a tool or code
I can use to automatically update an MDE to a new version. Basically do a
compare of objects and import new ones from a file. Want to be able to send
to clients and let them run it so I can bring them up to the latest version.

Would also be interested in anyone who has experience of doing an online
check for new versions of an Access database. Google did not throw up
anything of interest.


You should absolutely use a split database, with the tables in one shared
"backend" database and the forms, reports, queries etc. in a separate
frontend, with links to the tables. This is essential in a multiuser database,
but in your situation it's a good idea too. When you have a new form or
report, the user can simply delete their frontend (there's no data in it after
all!) and replace it with the new one.

Tony Toews has an automated frontend update which will simplify this process;
see http://www.granite.ab.ca/access and look at his Tips and Best Practices
links.

--

John W. Vinson [MVP]

  #4  
Old July 1st, 2009, 09:51 PM posted to microsoft.public.access
John W. Vinson
external usenet poster
 
Posts: 18,261
Default Update databases

On Tue, 30 Jun 2009 22:21:01 -0700, NevilleT
wrote:

Thanks John. I have a split database. Was looking to possibly do a couple
of things.
- When the program is opened, check a web site to see if updates available.
Maybe use an ftp download of a text file to check version number???
- Download an update if necessary.
- Check MSysObjects DateUpdate to see if objects need to be replaced.
- Delete objects and import new objects from the downloaded files.


Again:

If you're downloading an updated frontend, *simply delete the old frontend and
start using the new one*.

The frontend doesn't contain ANYTHING that the user has entered. The data is
all in the backend. There's no need to import anything.
--

John W. Vinson [MVP]
  #5  
Old July 1st, 2009, 11:08 PM posted to microsoft.public.access
NevilleT
external usenet poster
 
Posts: 159
Default Update databases

Thanks John. Agree with your comments. I was trying to be a bit too clever
and do it all from within the application. Just download a smaller file with
the changed objects and import those.

Working on a function to check online for the current version and decide if
something should be downloaded. Well progressed on this and should have it
working today or tomorrow.

Thanks for your help.

Neville Turbit
www.projectperfect.com.au

"John W. Vinson" wrote:

On Tue, 30 Jun 2009 22:21:01 -0700, NevilleT
wrote:

Thanks John. I have a split database. Was looking to possibly do a couple
of things.
- When the program is opened, check a web site to see if updates available.
Maybe use an ftp download of a text file to check version number???
- Download an update if necessary.
- Check MSysObjects DateUpdate to see if objects need to be replaced.
- Delete objects and import new objects from the downloaded files.


Again:

If you're downloading an updated frontend, *simply delete the old frontend and
start using the new one*.

The frontend doesn't contain ANYTHING that the user has entered. The data is
all in the backend. There's no need to import anything.
--

John W. Vinson [MVP]

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 01:30 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.