action queries not working when migrating to mainframe?

[Henrootje]

I have an existing frontend, connecting to a .mdb to a folder.

Now I am wondering whether it would be wise to move the tables in the
backend to a DBMS.
A colleague tells me that in that case, we have to rewrite all our
actionqueries.

Select queries would just use the linked tables in the tables screen
but all of the actionqueries would have (extensively) to be rewritten
into passthrough queries?

Any one can shed some light on that?

TIA Henro

[NthDegree via AccessMonster.com]

Would have helped a little to know the backend database engine but your
colleague is correct up to a point. If there is an ODBC available for Access
that handles your backend database engine it would make the change pretty
much transparent.

Henrootje wrote:

>I have an existing frontend, connecting to a .mdb to a folder.

Now I am wondering whether it would be wise to move the tables in the
backend to a DBMS.
A colleague tells me that in that case, we have to rewrite all our
actionqueries.

Select queries would just use the linked tables in the tables screen
but all of the actionqueries would have (extensively) to be rewritten
into passthrough queries?

Any one can shed some light on that?

TIA Henro

--
Never let it be said that I was totally comitted to sanity. It is the dark
places of my mind that fascinate me.

NthDegree

Message posted via http://www.accessmonster.com

[Henrootje]

Yes, ODBC would be involved. Would that mean that we do not have to
rewrite the actionqueries?
Would things work like they do with linked tables?
On 8 mrt, 15:33, "NthDegree via AccessMonster.com" <u29665@uwewrote:

Would have helped a little to know the backend database engine but your
colleague is correct up to a point. If there is an ODBC available for Access
that handles your backend database engine it would make the change pretty
much transparent.

Henrootje wrote:

I have an existing frontend, connecting to a .mdb to a folder.

Now I am wondering whether it would be wise to move the tables in the
backend to a DBMS.
A colleague tells me that in that case, we have to rewrite all our
actionqueries.

Select queries would just use the linked tables in the tables screen
but all of the actionqueries would have (extensively) to be rewritten
into passthrough queries?

Any one can shed some light on that?

TIA Henro

--
Never let it be said that I was totally comitted to sanity. It is the dark
places of my mind that fascinate me.

NthDegree

Message posted viahttp://www.accessmonster.com

[Larry Linson]

"Henrootje" <He****@gmail.comwrote

Yes, ODBC would be involved. Would that mean that
we do not have to rewrite the actionqueries?
Would things work like they do with linked tables?

I have worked with Access client applications linked by ODBC to various
server DBs since the days of Access 2.0, and I have never had to re-write an
action query. That does not mean, of course, that such a situation could
not arise, just that in the "normal business applications" I have dealt with
since 1994, I have not encountered it, so far.

So, it is clear that someone is either grossly misinformed or trying to use
"scare tactics" to convince you to take another approach when they tell you
that you will _have_ to rewrite _all_ your action queries. The use of such
"scare tactics" is not at all unusual when some entity which have a "vested
interest" in a different approach is involved in sales or planning, either
inside the organization or trying to sell their services to the
organization.

<POSSIBLY OFF-TOPICConsiderable rewrite and revision can be required,
however, if you are converting an Access MDB to an Access ADP. However,
their are third-party products which, for a price, can automate much more of
the conversion task than the supplied Micrsoft "upsizer" does. As I don't
recommend ADPs, I haven't employed any of them, and I certainly would not
venture to recommend a conversion software package to convert something I do
recommend (MDB with ODBC to Server) to something I don't recommend (ADP with
OLEdb). </POSSIBLY OFF-TOPIC>

Larry Linson
Microsoft Access MVP