Creating a rountine in Access to run thru an ODBC Connection

[hailadeel]

Afternoon,

I need help please, what I'm trying to do is via an established ODBC
connection to a DB2 platform run a routine so that I can change data
on the online screens using a table of information in Access.

For example, if I need to go to X= 27, Y = 019 and make the change
based off the information in table for instance. This is what I have
in mind to change phone numbers for 1000 customers

Establish connection and screen name then
(1) enter customer number (on db2.online screen)
(2) depress enter (on db2.online screen)
(3) get focus on position 26,137 (on db2.online screen)
(4) look up and apply access table.value 1 = 212-555-1212 (lookup in
access tbl.customer) apply to (on db2.online screen)
(5) press enter (on db2.online screen)

repeat

something like:

While (i=1, i++, i=1000) */ since there are
about 1000 changes to be made /*
{
Focus.application(access) */ switch to Access,
perhaps send keystroke ALT-TAB /*
Copy cell 1, row 1 from the array
Focus.application(terminal) */ switch to DB2 screen
name /*
Paste */ the cursor
would be placed on the default field, which is the corp. code id /*
Enter
Focus.application(Access)
Right Arrow, Copy
Focus.application(terminal)
TAB,TAB,TAB,TAB,TAB,TAB,TAB
Paste
Enter
Focus.application(Access)
Down arrow, left arrow
}

Any help would be great.
Thank you,
David

 

[dbahooker]

ODBC is depecrated; you would be better off using Access Data Projects
and landing your data into SQL Server

MDB is not reccomended for new projects

 

[Guest]

No.
If you have a DB2 screen, you do not want an Access Screen.

If you have an Access screen, you do not want a DB2 screen.

Both DB2 and Access have a database.
From Access you use ODBC to change things in a DB2 database.
From DB2 you can use ODBC to change things in an Access database.

If you want to use an Access Screen, just use DB2 to dump data
(access customer identifier) into a table. Then link Access to that
table and use the customer id to do whatever.

If you want to use a DB2 screen, just link the Access tables into
DB2, and write a DB2 screen to make the changes.

Switching focus between two applications is difficult for the
operator, takes twice as long, and always leads to data errors.

 

[dbahooker]

I agree with everything david says..


but id' reccomend using SQL Server as a desktop database, not MDB