![]() | |
#11
| |||
| |||
|
|
Search the application's directory(ies) or the entire hard drive for .fdl/.fsl, .rdl/.rsl, .ldl/.lsl - if you find these, it's Paradox the application; without these, it's not Paradox the application. You could also search for pdoxwin.exe or pdx*.* or pdox*.* and report the results here. If it's a Paradox app and you don't have the source code, you can't run it under any other version than what you've already got. If you've got source code, then we've got somewhere to start. (Sounds doubtful that you have the source.) However, any current version of Paradox would be able to read the data and write it out to nearly any format you could want. If you're going to stop using the application and migrate the data, I'd get Paradox; if you just want to keep using the app, I wouldn't touch the data (as far as editing data or altering structures) - though you could use Paradox to report on the data. NOTE: In your first post, you wrote: "most say version 5 is so outdated" - if this is really "level 5" of the tables, then, IMO, it's irrelevant - the table level doesn't matter all that much unless you need features of a later table level (and there's only one level after 5). If they're talking about the Paradox version, then yes, that's pretty old and made for Win 3.x, but it was a good version... Finally, we know you're using Paradox tables. There are certain requirements for that which are consistent no matter what the app is written in. I paste some tips below which will help you ensure the data doesn't corrupt (only major thing that's missing is to make sure the hardware (RAM, HDD, NIC, cabling, power, etc.) is all in good working order). 1. http://www.thedbcommunity.com/faq/13.htm [quoted text clipped - 27 lines] 6. Make sure the machine serving the .DB files isn't being used as a workstation. FWIW, Liz Is there a way to determine what the app was written in? And in that, can a newer version of paradox itself beloaded over the current version to at least keep those tables more current, or am I just whistling into the wind? |
#12
| |||
| |||
|
|
We have available the Borland Developer Studio 2006, however I am not familiar with it. |
#13
| |||
| |||
|
|
I am looking for any resources related to careware. A company is running Careware 3.18, and has had so much success with it that they don't want to upgrade. Oddly enough they are running XP Pro and I have been able to keep their Careware running with luck as we cross error messages and try to resolve them, however I am running out of resources and most say version 5 is so outdated. So how and why on earth would we stay with 3.18. When I look at the program it is very well designed. What the problem we are seeing is that the other versions or data bases that were taking over from them are causing other similar businesses nothing but problems. So we are staying with this one as long as we can. So any tips? Anyway we can save the data to be used with another program eventually without losing any of it. It is paradox based, any help or resources would be greatly appreciated. -- Message posted via http://www.dbmonster.com |
#14
| |||
| |||
|
|
I may be able to help, email me at numberjack (AT) wi (DOT) rr.com.nospam (remove .nospam) I am looking for any resources related to careware. A company is running Careware 3.18, and has had so much success with it [quoted text clipped - 19 lines] It is paradox based, any help or resources would be greatly appreciated. |
![]() |
| Thread Tools | |
| Display Modes | |
| |