Re: FN-FORUM: ASP/MS Access Help

date posted 24th August 2007 11:18

I agree with Leon. You're making this much harder than it need be by trying
to use duplicate tables.

If you're worried about updates going wrong then keep a log file of any data
which has been replaced.

----- Original Message -----
From: "Leon stacey" [EMAIL REMOVED]
To: [EMAIL REMOVED]
Sent: Friday, August 24, 2007 11:43 AM
Subject: Re: FN-FORUM: ASP/MS Access Help


>
> Hi Peter,
> That can all be done from one database then just use update behaviours in
> the update pages. I can see where you are going though with data in 2
> seperate tables, but I would always just use 1. Its always worked for me.
> With the consecutive number thing, that will need to be built into the MC
> access database.
>
> HTH
>
>>
>> I have created an ASP web page which is updateable via MS Access db. All
>> data
>> is stored in 1 table in the db, I have created a 2nd table which is
>> identical
>> and is used to display the data for the live page.
>>
>> Basically the user can make amendments to the web page and when there
>> happy
>> with it they click a button and all data is transferred from one table
>> to
>> another.
>>
>> At the moment I have created 3 script files:
>> script1: deletes the live db redirect to script2 with ID1
>> script2: gets the ID1 of the none live db, if EOF redirect to home page
>> script3: writes ID1 to live db, redirect back to script2 with ID2
>>
>> This works only if the ID numbers are in consecutive order,
>> unfortunately
>> they're not.
>>
>> Can anyone suggest another way of doing this?
>
>
>
> --
> Freelancers, contractors earn more with Prosperity4
> Call 0870 870 4414 or visit www.prosperity4.com
> and benefit from Inland Revenue approved expenses today.
>
> To advertise here: http://www.freelancers.net/advertising.html
>
>