Using Access 2003 linked fields in InfoPath SP1

D

Derangedseagull

Hi, We run retail software that uses Access 97 for its database, after
finding that infopath does not allow submitting to Access 97 (it is not
an option to update the database) we created an Access 2003 database
with the required fields we needed for a new job system and used Linked
fields to pull Customer details from our Access 97 database.

I then created an Infopath 2003 (not SP1) form to act as a front end to
all the data, everything worked well untill we updated to SP1 now that
we are running SP1 forms created Pre-SP1 continue to work but new forms
or modified forms will not accept linked fields they just deny their
existence.

Is it that support for linked fields was removed in SP1 or am I doing
something wrong?
Any help would be greatly apreciated

Regards
Tom Anderson
 
D

Derangedseagull

Does no one know the answer to this
need help desperatly

Regards
Tom Anderson
 
J

Josh Bertsch [MSFT]

There is work being done to understand your situation and if a problem
exists in SP1. An answer will be posted when there is a resolution.

Thanks.

--josh bertsch
 
D

Derangedseagull

No Errors. Just that the fields that are linked are non existant in
Infopath Eg. they it will show me all the tables in the access database
but any linked tables are not listed and so cannot be used.
Thanks very much for your help

Regards
Tom Anderson
 
T

Tom Curtin

I came across the same behavior with linked tables in SP1, since I hadn't had
experieince with the earlier version I assumed it was a limitation and simply
went directly to the linked table. Is this a feature or a bug?
 
N

Nick Dallett [MSFT]

Could I get a detailed description of exactly what you're doing when you see
this issue? I tried setting up a linked database, and I had no such
problem. Caveats: 1. I'm using an internal build of the product that is
more recent than SP1, 2. I'm using Access 2003 and saving the linked
database as "Access 97 format" (rather than using a native Access 97
database). If you could describe in detail:

- your database structure
- the exact steps you're going through to set up the links in Access
- the exact steps you're going through to set up the InfoPath Form

--
Nick Dallett
Program Manager, Microsoft Office InfoPath

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm. Please do not send email
directly to this address. This address is for newsgroup purposes only.
 
N

Nick Dallett [MSFT]

Update:

I tried this again on a computer running Office 2003 SP1, using a native
Access 97 database that I found on the web (same scenario as yours - it's a
legacy freeware app that uses Access97). Everything worked smoothly.
Here's what I did, for comparison:

1. I created a new Access 2003 database, and added one table
2. I chose tables-->link tables
3. I browsed to my access97 database, and chose all tables. OK'ed out of
the dialogs
4. I closed Access
5. Opened InfoPath and chose "design a form"
6. New from data connection
7. Chose database and went through the wizard to point to my new Access
2003 DB
8. Added one of the linked tables from my db
9. OKed out of the dialogs
10. Added a repeating table to my data view with all fields
11. clicked "preview form"
12. clicked the "query" button
13. All rows from the DB showed in my data view

I can also submit without a problem, and requery the new data, with or
without parameters.

You might want to try going to the data connections dialog in your solution
(Tools-->Data Connections), click "Modify", and then click through the
wizard again to re-link to the database. That might give you some clue as
to what's going on.

Other than that, is there anything I'm missing in your scenario?

--
Nick Dallett
Program Manager, Microsoft Office InfoPath

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm. Please do not send email
directly to this address. This address is for newsgroup purposes only.
 
T

Tom Curtin

no, but it still doesn't seem to work that way for me. I've tried it on
several PC's at my company and am getting the same result. I'm still
thinking its an access issue since as I said the same behavior occurs if you
attempt to do the double jump from another access database.
 
T

Tom Anderson

Hi Nick,
Thanks for all your help. I followed your steps exactly and had
absolutly no problems creating linked tables, i also went back to Pre
SP1 and had no problems. I then attempted to use the actualy database
(with actual data about 600 entries into the variouse fields) and it
would not work with SP1 or Pre-SP1 so i am assuming somthing has
altered in the database that no longer allows Infopath to link to it
properly. The problem is thus;

The databse has two tables that are not linked but are in that
database (an access 2003 database) it also has two linked tables that
link back to an access 97 database. The two linked tables come up as
odd names eg E7501 with fields E73033, E73032 ect. odd huh.

If i create a new database and link some tables it works prefectly, so
i have no idea what has changed in the real database (also ONLY
infopath access's this database nothing else so no changes should have
been made).

On a side note the only reason im using linked tables is because with
InfoPath pre-SP1 it would not allow submitting on an access 97
database (Native) can you confirm that i can perform submits on an
access 97 database and if so ill just re-write the infopath form.

Oh and even thou the linked tables seem to come up corrupt when in
design mode the Infopath forms that were made prior to SP1 still
constinue to function flawlessly its just that i would like to add
more functionality to the form.

Regards
Tom Anderson

P.S thanks very much for your help!
 
Top