geraintcollins
asked on
Foxpro limitations
Hi,
A client has asked me to take a look at a foxpro backend and access frontend system. The issue the client is having is that no one has any foxpro experience as the developer has long since gone. I've yet to see the application but it would be good to know if there are any solid reasons to move away from this architecture i.e. are there any know limitations with foxpro. (I will be finding out the version number tomorrow but I suspect is an old version of foxpro).
I may be advising the clinet to move to an access backend and frontend design so the more reasons I can give the better.
Thanks
A client has asked me to take a look at a foxpro backend and access frontend system. The issue the client is having is that no one has any foxpro experience as the developer has long since gone. I've yet to see the application but it would be good to know if there are any solid reasons to move away from this architecture i.e. are there any know limitations with foxpro. (I will be finding out the version number tomorrow but I suspect is an old version of foxpro).
I may be advising the clinet to move to an access backend and frontend design so the more reasons I can give the better.
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Nico...good to have you back..mike
Thanks Mike, I'm here to stay :-)
Nic;o)
Nic;o)
ASKER
ok so I've met with the client and its foxpro 2.6 - (released in 1989!). He's happy to migrate to Access. Any ideas how to import the data from fox pro 2.6? Not surprisingly the dbf import options in access won't do it.
Did you try to install the Focpro 2.6 on your PC ?
Then the standard import using filetype .dbf might work like it did for me.
Nic;o)
Then the standard import using filetype .dbf might work like it did for me.
Nic;o)
ASKER
Yes but I keep getting the error message "external table not in the expected file format" when I try importing the dbf.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the information. I found that the problem was due to a foxpro numeric column containing non-numeric data. I changed the data type to character and it imported. I'll distribute the points accordingly.
ASKER
had to increase the points to split them three ways