Foxpro is perfectly OK. It is a database with application programming as is Access. There is no point in comparing one with the other. Your strategy will be driven by what your employer wants to do. If you have to support it then there may be a case for getting rid of either Foxpro or Access depending on available skill-sets. If it is outsourced to India, that might not apply. Or maybe you need the data all moved to a corporate MS SQL Server environment. It's these sorts of issues that drive IT decisions.
You should be able to migrate data easily from Foxpro (with utilities) or possibly connect to the Foxpro tables from Access.
Access is mainly Visual Basic and SQL. This fits in with the current general Microsoft World. Foxpro by contrast is yesterday's product. Foxpro incidentally hails from the line of databases known as 'tabular' - before people had developed coding strategies to implement relational databases, at least on pcs.