Soldato
- Joined
- 26 Apr 2004
- Posts
- 9,789
- Location
- Milton Keynes
I'm not hugely coding literate, I've done bits and pieces of HMTL etc before now for this and that, but nothing very complex.
I'm going to try and have a look through the coding guides/tutorials listed in the help thread...but there's lots of them!
Ideally what I'm looking to do is make my work a little easier.
At the moment we have to try and log certain bits of information when they come in; however at the moment the IS guys have it setup as a basic one person accessible spreadsheet...not really ideal.
What I'd like to ideally do is code a webpage that allows you to fill in some data in pre specified fields, click apply/save, and then the data filled in will be logged into a table/list, each time being logged as a seperate entry (so as to avoid bits from one entry getting mingled with another if the previous entry didn't require this).
As the backend is only being updated when one of us clicked send, this would eliminate the single user problem.
I'd also like to be able to set it up so you could then view this list, but that shouldn't be too hard once the initial database/page has been setup.
I'm also going to look into doing this via access, as I used that years ago, but ideally a web based method that could be used on multiple browsers would be a little more suitable; as I doubt everyone has access
Any suggestions?
(Major thanks in advance)
I'm going to try and have a look through the coding guides/tutorials listed in the help thread...but there's lots of them!
Ideally what I'm looking to do is make my work a little easier.
At the moment we have to try and log certain bits of information when they come in; however at the moment the IS guys have it setup as a basic one person accessible spreadsheet...not really ideal.
What I'd like to ideally do is code a webpage that allows you to fill in some data in pre specified fields, click apply/save, and then the data filled in will be logged into a table/list, each time being logged as a seperate entry (so as to avoid bits from one entry getting mingled with another if the previous entry didn't require this).
As the backend is only being updated when one of us clicked send, this would eliminate the single user problem.
I'd also like to be able to set it up so you could then view this list, but that shouldn't be too hard once the initial database/page has been setup.
I'm also going to look into doing this via access, as I used that years ago, but ideally a web based method that could be used on multiple browsers would be a little more suitable; as I doubt everyone has access

Any suggestions?
(Major thanks in advance)