Sarah
It just dawned on me (Yes, I'm a bit slow at times) you cannot put a data macro on a linked table of any kind. Linked tables can't have their design changed from the front end. An Access back end could have data macros, but a SQL back end would have to have triggers.
So to answer your question about being able to have either Access tables or SQL tables, yes you can do that. You just have to do the triggers and data macros in the appropriate places.
Bill
---In ms_access_professionals@yahoogroups.com, <sarahk@schemesoftware.com> wrote:
Bill,
So what do you mean?. I need to rewrite an old ERP application and was thinking of rewriting it in Access. Smaller customers could you an Access DB back end and larger ones an Sql Express back end. Are you saying that this is not the way to go?
Sarah
---In MS_Access_Professionals@yahoogroups.com, <ms_access_professionals@yahoogroups.com> wrote:
Jim
They are actually more like triggers in SQL Server. They fire when a field is changed or added/deleted. One good use is to update a field like ModifiedBy where you want to keep track of the last person who updated a field. It's easier than writing code for it and is probably the only way to do it when it comes to web forms since you can't use VBA with those.
Like John, I haven't explored this new feature mainly because I use SQL Server databases for most of my back ends. Access is definately movong away from desktop databases. That might be good for some, but I'm not thrilled about it. Eventually, I know I'll have to move from Access to something like C#. But until then I'll stick with VBA.
---In MS_Access_Professionals@yahoogroups.com, <ms_access_professionals@yahoogroups.com> wrote:
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (11) |
Tidak ada komentar:
Posting Komentar