Recovering a split access database

[earflea]

I recently used a splitit program to split an Access mdb file in two parts so
that they could fit on a pair of floppies. The splitit program I used was
deleted after a virus attack and I do not know the name of the program. I
have tried to use various splitit programs to merge the pair back together
again. Two of them produced a merged program, and I have also tried to merge
them with a DOS copy /B file + file command which also produced a merged
program. In all three cases it was rejected by Access as "unrecognizable
database format". So I cannot be sure whether the original split, the
attempted merges. or Access were at fault. What I do know is that I am
desperate to recover the database. Can any member give me a suggestion? I am
running XP PRO and Access 10 with lots of disk space and memory.

 

[DL]

Do you mean you used an app. to 'split' a *file* across multiple floppies?
Rather like spanning using winzip or winrar?
What is the attribute of the resulting file on the floppies?
BTW its rare for a virus to delete an app. - more commonly its the user!

 

[earflea]

There are a number of "Splitit" programs (try googling that word) which will
cut an original file into smaller parts. This is usually done because the
size of the original file is too large for a floppy disk. The same programs
provide means of putting the parts together again to provide the identical
original file. The attributes of the part files are the same as those of the
original file. Your point about a virus is apt. I shortened the causal
chain. The virus made my computer increasingly unstable and I was forced to
reinstall the OS - in that process I lost some files which I think is
inevitable, but in any case I am perfectly happy to bear the blame. The
problem is how do I join the two halves of the original file together. I am
not a programmer but it seems to me that all the data in the original file
must be in the halves, plus some kind of linking mechanism. That shouldn't
be insoluble. Thanks for your post.