Search results

All righty..... So here we go.... CJ and everyone out here who helped me.... I would like to give a huge applaud of thanks to everyone and thanks a lot to CJ who stuck with me till the very end.... I was able to successfully link all the tables to the C: drive where i had created the new...

So now i would go ahead and start the linking and see if it gets linked to the C: and not Z: Will keep you posted.... Thanks for helping me sort it out

So what i did was I created a new database and then went to new onto the database window and selected New--> Link Tables --> Gave it the location of the shared database (which i shared from other working system on which the database is working) --> Select All --> Ok... Now we have all the...

I understand that what are you saying.... And I am sorry for taking a huge amount of time of yours.... Lets Say if I start with a new data base file and then import the tables from the other system .... Will that solve the purpose.... Just an assumption if you can help ?

Have tried that as well but does not help.... Sorry did not post that previously... If i double click it will open the Transaction / Values

I tried it with right click but i do not have the option to rename... It gives me properties design and open and if i go to properties there also is no option to rename..... So we are stuck again.... My second system which also has access 97 and windows xp runs good....

So after a long time of working around I was able to to open up the linked table manager by using the shift key to open the database file first and then coming to Tools--> Addins --> Linked Table Manager.... Now this opened a new windows for me and it showed me that all my files were hooked...

Dear Nauticle, Thanks for your reply, however I would like to let you know that this is Access 97 and that I am not getting the option of Database Tools over here.... If i use the Shift key and then try to open it opens all the tables but it does not have the option to show me the databse...

When i hit Debug this is the line that is highlighted.... Set Pref = CurDB.OpenRecordset("Preferences", DB_OPEN_DYNASET).... If you can let me know what do i need to do at this point of time.... I checked the code on the other two systems and they both say the same coding....

Ok I was in the process of importing the tables when i got this message that : Z:\hayess~1\Data\Yes4\yeshayea.mdb is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server onto which the file resides... I hit Ok 3 -4 times and then it gave...

yes i followed that step and that is what is the screenshot i have attached....

Hi Please find the file attached when i try to open the database file while holding down the shift key.... Also In reply to the below queries are my responses: 1. you say you don't use any coding, but attach a screenshot of some. This VBA comes up when i press debug if i press...

As I mentioned earlier that we do not use any coding and it just a database file..... For the very same reason have attached both the error code and the VBA script as well..... So if you can please go through it and then let me know.... I would not be able to check the linking of the table as...

Re: "Microsoft Access can't start because there is no license for it on this machine" Dear Crilen007.... I signed up just to thank you as to how detailed your explanation was and how it helped me in getting the issue resolved..... However now after that, i get a different error message which...

Here is the screenshot of the same... The error happens when I try to open the Access database.... The file opens good on other two systems but unfortunately not on mine... It is in the zip file as the size was exceeding the limit... Also, i am attaching the VBA code as well however we...

Hi Ranman, I will do it now.... Sorry for that.... Will post the error in next reply.... Thanks....

I am getting a runtime error while starting my database file as follows: MICROSOFT ACCESS RUN TIME ERROR 3044 C:\Hayes Server\Data\yes4\yeshaeya.mdb is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server onto which the file resides. I...