Access project no more support instead of triggers

M

Martins

In specific situation we used INSTEAD OF triggers for business logic, that
will have to execute before record was actually added to table.

Martins.
 
A

aaron.kempf

yah I've just never heard of anyone actually using those before. It's
fascinating; I'm sure in a parallel universe I could have used them if
I had stuck around.. lol

What would interest me more-- back in the Sybase days-- there was talk
of giving us a 'Select Trigger'.
I still think that would be the greatest thing since sliced bread. I
mean honestly.

That way-- if someone asks for a table; we could decide to filter the
record for particular rows.. etc-- it would give us real row-level
security.

Are you trying to do something similiar with instead of ?
Are you using Stored Procedures?

Can I see some code so I can helpfully help you to solve this?

Thanks

I'd just love to see more about your instead of triggers; I've really
honestly never met anyone that uses them.
I love ADP. I've just been afk these past 6 months and haven't been
able to flame people about ADP lol

-Aaron
 
M

Martins

Thanks Aaron for interesting in this particular case.
I agree that IO triggers are very specific, and better avoid using it.

But in Access case when user adds new row in form, and Access imselft hangle
that and do other work with record putting in table and retriving from table,
it's very easily to add some server business logic in trigger. 99% of over
triggers are AFTER triggers, but we have some specific cases when we need to
do some work before record are actually inserted in table. And it that
situation we use IO triggers.

I know how to redesign application. I'm just disappointed that we have to do
that (what will take time and money).

Martins.
 
A

aaron.kempf

Yah I'm the biggest ADP fan ever. You've probably seen my rambling
about ADP over the years... ROFL

I actually worked in the Microsoft Marketing department.. until just a
few months ago.. I wish I would have stuck around and made a
difference.

I honestly think that ADP is the biggest defeat that Microsoft has
ever suffered.
Microsoft shouldn't be spending $44 billion on Yahoo.. They should be
spending $44 billion making SQL Server and Access work together
properly and consistently.

Honestly. I would rather Microsoft take Oracle seriously-- than
Google. That's my career- SQL Server - so they got my vote.

They talk growing in new directions-- I am positive that Microsoft
could double their presence in the SQL Server world by making ADP
prevalent and bulletproof and as easy to use as Excel.

It seems to me like a no-brainer; best system anywhere.

It makes normal Access kids into SQL Server gurus.. It's just a ton of
wasted potential on Microsoft's part I think.

It should integrate with SQL Server Reporting Services.. It should
work with Analysis Services.

ADP should integrate with SSIS.

Access should merge with InfoPath and they should bring back Office
Web Components and make that a main piece of 'Excel Services'.
Because InfoPath was basically the extension of DAP-- and I think that
it's all the domain of the ADP department.

But it just breaks my heart-- we're going to have to wait for yet
another 'new version of Access' for the best ADP. I've seen the
powerPoints; it is coming.

Thanks and Good Luck-- I'd love to trade notes on ADP sometime ;) I've
done hundreds I think

-Aaron
MCITP: Database Administrator
(253)
 
T

Tony Toews [MVP]

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top