Are Table Triggers supported

[Eyespi20]

Ok, I'll confess to being a SQL person, so Access is proving to be a huge learning curve.

Does it support triggers? I need to insert rows into another table when the first table is updated (keep a history of actions). If triggers are not supported, what would be the best method of achieving the same result?

Thanks in advance for your help!

Margaret

 

[jrbarnett]

Access / JET does not support triggers at all. What you would need to do was have code in a form that was executed in the appropriate event handler of a form - to insert the records into the history table.

John

 

[BNPMike]

I'll confess to being a SQL person

I assume you mean MS SQL Server. If you are used to that then why not base your Access application on it? Access comes with the MSDE version of MS SQL Server.

See

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmsde/html/msdeforvs.asp

 

[Eyespi20]

John: We are pulling information from one of our SQL Servers and using Access' switchboard to enable users to update/insert information into the other SQL Server. It may not be the most elegant solution to our situation, but it's what we have to work with and allows us to spend our $$ on other things right now.

Thanks for your input.

Margaret

 

[PHV]

As the real datas are on SQL servers, you may consider playing only with linked tables in access and implementing the triggers in SQL server.

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244

 

[BNPMike]

You can extract data from one SQL Server database and insert it into a different one. Access is very good at that. It was Microsoft's Universal Data Access (or something similar-sounding) vision.

 

[Eyespi20]

What we have done is extract via query into an Access db table which the switchboard is the tool for which we use to update the records. I want to keep a history of the records that were changed (from on contract to off contract as our customer changes this like you and I change underwear)which is where my trigger question comes from. The table will reside in the Access database and be accessible to our sales staff for the next time we renew the contract with the customer. All this on/off is time consuming and then we have credit/rebill which is also time consuming, but the contract amount is not enough to cover what it's supposed to cover PLUS the administrative costs we're encountering. By recording the history of the on/off, we'll be able to provide documentation and justification for a request to increase contract billing.

The rest of the functionality is that it actually CREATES the contract invoicing which will save our AR person countless hours of data entry.

Yes, I could do it all in SQL Server, but at a cost to my production server efficiency. This will keep it local and web-enabled for my field at a lower cost overall.

Thank you all for your input. This has been very educational!

Margaret