Sorry, not possible. Access doesn't support any triggers. You can, of course, write code to deal with lots of instances, but in some cases you end up SOL on this one.
Would it work to write sql to do the work after the data have been imported? It doesn't give you the same assurance as a trigger, but if you make sure the import is only run as part of code that also fires the sql to do the follow-on work, that should be sufficient for a lot of purposes, if not all.
Please post in the appropriate forum with a descriptive subject; code and SQL, if referenced; and expected results. See thread181-473997 for more pointers.
Since the update will be done at the code level, only rules defined for the tables and design schema will be enforced. (I.e., primary key, referential integrity.)
(This is one of the reasons why updating via ODBC or other external means can be dangerous.)
So what are you trying to do? Will the ADO updates be done from an external or internal source?
I have a VB6 program which searches a Word document (that has been downloaded to the server by the ASP code) for keywords.
I think will have to either run the executable from the ASP code or convert the code to VBA and somehow to a Create.Object ("Access.Application" from ASP. I think the latter is a more secure method of doing this.
The ADO update is executed from the local ASP page.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.