Database Split problems

[Guest]

I'm trying to split my database but I keep getting two errors... First,
"Subscript out of range" immediately followed by "Invalid procedure call or
argument." and no further information.

How can I find out what my problem is? I can't seem to find any
troubleshooter or documentation that assists me.

I'm using 2003 format and I have several linked tables using ODBC (FoxPro).

Thanks in advance.

 

[Albert D.Kallal]

Well, since FoxPro tables are in effect linked tables..then they really
don't change in a split database (in fact, this just means the ms-access
tables now become linked tables like the FoxPro ones).

I would suggest that you try deleting one of the FoxPro "links"...and then
re-link that FoxPro table. Since they are always linked tables, then you
should be able to get this to work.....

 

[Guest]

Relinking one table did not do the job...

I opened the Linked table manager and noticed that some of my links are
"Visual FoxPro Database" and others are "Visual FoxPro Tables." Could this be
part of the problem?

 

[Albert D.Kallal]

So, you saying that the un-split application, the FoxPro tables are ok...but
not in the new?

Try deleting and then creating a linked FoxPro table in the un-split
application (well...ok...a copy just in case you mess this up!!)...the
process should NOT make any difference here.

It is seems to me (so far), the problem is simply linking to FoxPro...and
not a issues of splitting?

Anyway, why not just split manually then..and not use the wizard?
( a good many posters state that they don't use the database splitter
anyway).

Just create a blank mdb file...and then import all the tables from the front
end....

Now, delete all your data tables in the front end..and simply link them to
the back end (this way, you will NOT touch your working FoxPro tables).

(in other words, don't delete the linked FoxPro tables...just leave them in
place...and ONLY delete the ms-access tables which you just copied to the
new back end mdb).

 

[Guest]

Ok... that is simple enough. I always wondered if I couldn't just do that...

I am curious though, should the front end be linked directly to the FoxPro
tables or should they go through the back end to link? I'll be having four or
five users on the front end and I want to set up now for optimal growth in
the future.

 

[Albert D.Kallal]

I am not aware that you can "link" to a "link"...(and, if you could..it
would seem a waste anyway).

So, no...I don't think can even do that anyway.

Really, if you think about this..you have a similar case for the fox and
access tables. Your front end is simply a link to them....