DotDragnet
May 21, 2012, 06:12:40 PM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Mobile users - Our forum is Tapatalk enabled. http://www.tapatalk.com/
 
   Home   Help Search Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: Access Database  (Read 2620 times)
steve_c
Newbie
*
Posts: 15



View Profile Awards
« on: June 14, 2007, 10:24:38 AM »

Hi all - this one is quite annoying!  A site I'm creating at the moment requires me to run it off of an access database.  Site created using ASP.Net.  The database needs to be updated around once a week but off course the data.mdb file is always locked when I try to upload the new one, is there any othe rway to achieve this other than deleting the web.config file, thereby disabling the application and then uploading the new file?

TIA.

Steve.
Logged
Curry
Guest
« Reply #1 on: June 14, 2007, 10:47:04 AM »

Why does the db need to be uploaded?

I would say you need to look at having the database updated online. Not offline and uploaded over the *live* db as this will allways be a pain in the bum for you.


hth

Matt
Logged
sickpuppy
Site Chimp
Administrator
Hero Member
*****
Posts: 1912



sickpuppysoftwa
View Profile WWW Awards
« Reply #2 on: June 14, 2007, 10:56:33 AM »

Are you just updating the data within or the structure?

If it's just the data then you could run a series of insert statements against the database.
Logged

steve_c
Newbie
*
Posts: 15



View Profile Awards
« Reply #3 on: June 14, 2007, 11:43:17 AM »

Just updating the data - how would I do the update statements?  The mdb file is located on the client's local machine.

*edit* I should mention that they update the database locally (it's a findaproperty database) and they don't want to have to update the data twice (once for findaproperty and once for their site)
« Last Edit: June 14, 2007, 11:50:48 AM by steve_c » Logged
Curry
Guest
« Reply #4 on: June 14, 2007, 11:55:05 AM »

Just updating the data - how would I do the update statements?  The mdb file is located on the client's local machine.

*edit* I should mention that they update the database locally (it's a findaproperty database) and they don't want to have to update the data twice (once for findaproperty and once for their site)


Can they not update the web site via an online script and download the updated DB for use locally.

Use an online form to collect the data for entry. Then update the DB via a SQL statement.

http://www.w3schools.com/sql/sql_insert.asp

hth


Matt
« Last Edit: June 14, 2007, 11:58:04 AM by Mr Curry » Logged
steve_c
Newbie
*
Posts: 15



View Profile Awards
« Reply #5 on: June 14, 2007, 11:57:54 AM »

It's a weird situation.  They are a letting agency which use findaproperty.com to list all of their properties.  They use the FAP windows app which once they click update, sends the mdb to findaproperty.com.  So they have their properties both locally and on findaproperty.

I based the new site around this mdb file, to save them entering in the data twice.  But cannot for the life of me think of how to get the data updated on their own site.
Logged
Curry
Guest
« Reply #6 on: June 14, 2007, 11:59:26 AM »

It's a weird situation.  They are a letting agency which use findaproperty.com to list all of their properties.  They use the FAP windows app which once they click update, sends the mdb to findaproperty.com.  So they have their properties both locally and on findaproperty.

I based the new site around this mdb file, to save them entering in the data twice.  But cannot for the life of me think of how to get the data updated on their own site.

Can they not update the web site via an online script and download the updated DB for sending to findaproperty.com
Logged
steve_c
Newbie
*
Posts: 15



View Profile Awards
« Reply #7 on: June 14, 2007, 05:07:57 PM »

Thanks for the help - in the end I decided to create a winform app which ftps into the web app, deletes the web.config file, which unlocks the db, upload the new data.mdb and then upload the original web.config, therefore reseting the application.

Seems to work ok.
Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF | SMF © 2006-2008, Simple Machines Valid XHTML 1.0! Valid CSS!