OLD MEDICAL PROGRAM IN ACCESS 1.1 CONVERTED TO 2003, DOES NOT RUN.
Thanks Mr. Wachal.
We did everything exactly what you have suggested us to do. The MDB file is now in Access 2003. BUT, BUT, the program, that was written over 12 years ago, does not understand the new file. It is not able to open the file. It seems that the old software only understands Access 1.0 or 1.1 MDB files. So, what can I do to with this old medical software, wery useful and practical, but unable to be upgraded with a newer data base file type?
Really, thanks for your kind help and excellent advices. You are the only chance that we have to solve this problem, so thanks again.
Dr. G. Varnagy
Caracas - Venezuela
[682 byte] By [
Dr.GV] at [2007-12-20]
1. DO NOT SHOUT !!!
2. if you're replying to someone who has already helped you, do so on that thread. Then the exchange will make sense to anyone who reads it, and the person you're talking to will get an email to say you've responded.
3. I'm not surprised to find that Access has changed over the past 12 years. I'd guess that you'd need to work through the app and change the code where-ever it breaks to reflect VBA in Access 2003.
By the way, SQL Express is the wrong forum to ask this question, as far as I can see, a VBA forum would be the most likely choice.
I see that someone suggested that you repost this as a new question, I would have changed the wording, but that's fine. It seems to me that you have your data, and perhaps after 12 years, it's not unreasonable to suggest that you'll need to pay someone to write a new app, which uses that data in Access 2003.
1. Thanks, and sorry, but it's a desesperate situation.
2.- We don't have the program codes and there is no way to get them.
3.- I could not find here in Caracas nobody able to create such a simple but very functional medical office program, that uses data and images for each patient. The young lady that created our program had twins and did not answer our calls.
4.- So please, if it is any way you or somebudy in this forum that can help, it will be highly appretieded.
Dr. G.Varnagy
Hi!
Was this entire program made using Access 1.1 or is it a separate program ".exe" that reads data from an Access .mdb file?
If it is a seperate program, you are out of luck without the original source code to work with. Your only choice would be to have someone build a new prgram from scratch.
If it is all made in Access, it might be possible to re-work it into newer version. You would still need to to pretty much build a new application, but I think it would be easier going.
Doug
Hi, im helping Dr. V to migrate his medical software from VB 3.0 (GUI) and Access 1.1 (DB), to a newer technology. Here's what i've have been done so far:
- I used MS Access 2003 to import the tables Access 1.1, i created an odbc link to the old database and i had no problems with de migration of the data.
- I replaced the old .mdb file with the newer .mdb (Access 2003) in the VB 3.0 program's folder. But I cant open the program because it does not recognize the new file.
- Dr. V tried to contact the developer of the old VB 3.0 file but she doesn't have the source codes.
Is there any way to connect this VB 3.0 app to MS Access 2003 database? or to MS SQL Server 2000? , The objective im trying to acomplish is to change the database engine to another that supports more data ( > 1GB) without changing the app nor re writing a new one.
I will apreciate any help
Thanks
Miguel
Hi Miguel,
Without the source code you're in a tight spot, but here are a few wild ideas you could try:
- If the application has the ability to archive data, you could remove some of the data from the original database so that it will continue working. (Probably just a stop gap measure here to give you time to re-write the application.)
- If the application uses ODBC to connect to the Jet database, you could look in the ODBC Administrator to see if there is a DSN that the application uses to connect to the database. If there is a DSN, you could try updating the DSN to use the Jet 4.0 driver rather than the Jet 1.0 driver.
- If the application stores it's connection string in a settings file rather than having it compiled into the application, you could try to modify the connection string to use the correct Jet 4.0 driver.
Like I said, these are really out there, but without source code, there isn't much you can do. To be honest, I'm not even sure if VB 3.0 would support using the Jet 4.0 ODBC drivers.
Even if any of these methods work, you should probably consider updating the application, either by contracting the original developer to do the work or doing it yourself. Access has come a long way as a development tools since version 1.1, so it's possible you could move the application directly into Access 2003 rather than using VB. If you wanted to stick with VB, you can check out VB .NET 2005 Express Edition, which is free.
This is best I can come up with.
Regards,
Mike Wachal
SQL Express team
-
Please mark your thread as Answered when you get your solution.
