G
Guest
I'm working on a ticket writer database. Currently, it has about 10-15
ticket agents using it simultaneously. There is also a read-only 'ticket
portal'
which users may use the retrieve a ticket. This is an classic ASP web page
on our
internal network and uses OLEDB to access the Jet database via an ADODB
connection. The database is not on a web server but is on a shared network
drive. The owners now want to be able to write to the database via the
portal. This would be implemented with .Net. Has anyone done anything like
this? What considerations come into play? Can the table being updated this
way also be updated via the Access database or can it only be viewed? How
does the LDB file behave regarding the web-based accesses.
ticket agents using it simultaneously. There is also a read-only 'ticket
portal'
which users may use the retrieve a ticket. This is an classic ASP web page
on our
internal network and uses OLEDB to access the Jet database via an ADODB
connection. The database is not on a web server but is on a shared network
drive. The owners now want to be able to write to the database via the
portal. This would be implemented with .Net. Has anyone done anything like
this? What considerations come into play? Can the table being updated this
way also be updated via the Access database or can it only be viewed? How
does the LDB file behave regarding the web-based accesses.