OK. I'll try to answer all the above points at once ...
You've not actually said why you want to create a new copy of your db.
This is usually only done when the old db is experiencing issues or unexpected behaviour. The most likely reasons for this are:
a) corrupted data in one or more tables
b) corrupted code or corrupted database objects (form/report etc)
c) missing VBA references
The fact that only your queries import without error suggest a) and/or b) are true
Also you've tried running your db in Access 2007 before reverting to 2003. This may well mean that c) is true
You say that you did all the steps I listed but the fact that nothing has changed suggests to me that you omitted some or all of this part:
If you have any corrupted data in one or more tables, you will need to fix that first
If the code itself is corrupted, first make a copy, decompile it then recompile & finally compact it.
If you did, that was a mistake... you NEED to check / do all of this
BTW: I've added one extra step to my original post -
in RED. I'll explain this in a minute ....
OK back to your comments
1. Access Version
First I am using access 2003.
That's not relevant here.
Everything I wrote should apply to all versions as far as I'm aware
2. VBA References
Second I don't understand ADD VBA Refrences??!
ALL Access databases use a number of reference libraries in order to run VBA code.
Some are installed by default but developers often add more...
See screenshot for a typical VBA reference list
When you change to a newer version of Access, the references are usually upgraded. However reverting to an earlier version doesn't work so well as the older version may not recognise the reference. If so, the 'broken' reference is flagged as MISSING and some program code may not work
Check your references by opening the
Visual Basic Editor (VBE)
e.g. using the keyboard shortcut Alt+F11.
Then go to
Tools ... References and check whether any are MISSING
If so, you will need to browse for these to reinstall a working reference
3. Import Errors
Almost certainly, you have corruption somewhere
Check each table in turn looking for record where data looks 'odd' e.g. the text may appear to be in an unknown foreign language rather than standard characters.
If you find anything like that you'll need to delete the affected record(s) BEFORE importing to the new db
Alternatively make a copy then EMPTY the tables so you can import without that being an issue
Similarly with forms, reports etc.
If any are corrupted they may cause errors on importing.
EITHER open each item in turn in the old db & check ...
OR import one object at a time so you know which item(s) cause the errors
4. Decompile, recompile then compact
Decompiling is used to remove compilation code e.g. if its corrupted...
To do so you need to open Access in a special decompile mode.
See the previous link for instructions
Compiling - this is necessary to check that all the code will run without error.
To do this open the VBE, click Debug then Compile
This should only take a few seconds if all is OK
If it fails, you'll need to fix the error - the problem code will be shown in
RED
COMPACT
When items are removed from a db, the space taken isn't recovered automatically
Compact & repair the database to reduce its size.
I'm not using Access 2003 but its probably in the Tools menu
Again it won't take long and the db may well shrink significantly
In fact after you've done all the above your db may well be perfect and the need for a new copy become redundant !
5. Uploading the db
I said I would look at this
as a last resort.
In other words after you've tried EVERYTHING yourself
There are 2 reasons for this
a) if you fix it yourself, you will understand the cause of the problems better
b) I'm using Access 2010/2016.
If I fix your db, you will probably have to fix the references again ! (see above)
To reduce the file size, you will NEED to remove almost all of the data anyway & then compact the db again
See this link for further info
https://access-programmers.co.uk/forums/showthread.php?t=140587
Hopefully the above hasn't put you off ...
If it has, you can always pay a specialist company to do the job for you but it will cost a tidy sum!
Let me know how you get on