The way One Drive works you don't just have one online table as in a hosted database.
Every user gets a copy of the DBF to his local drive. Every change to that DBF works, but eventually leads to syncing that file with OneDrive.
In the end you have the same problem as with PACK, everytime you only just add a record or update one, OneDrive uploads the whole file online.
Just assume a simple starting situation and what happens. Two users have a DBF from the online OneDrive in version X with 100 records. Now user1 adds 1 record to his DBF and ONeDrive uploads that. This causes the other users PC to sync the new DBF version with 101 records, but when he already also added one record in his outdated 100 record version, either his record will be overwritten when his DBF file is overwritten from OneDrive or his DBF with his 101st record is uploaded to OneDrive. In any case, only one record of both remains. And that's still a good case, in the worst case such conflicts lead to file corruptions.
To summarize, OneDrive (and other cloud drive solutions) are syncing files on the basis of whole files, not single records within them, that's not what works well.
Mike told you there are better solutions to have DBFs in the internet, one is establishing a larger LAN, a WAN. There's hardware specific to that, ie routers with WAN feature, there are software solutions. I never set up a WAN, but you find threads about this solution.
Data in the internet is better put into a database server like MySQL, which would eed a rewrite database and all data access. It's something you should consider before even starting to program, because you're now either stuck with the DBFs and ways to host them or you have to reimplement a portion of your code.
Just to give a hint: A MySQL, MariaDB, PostGreSQL, MSSQL or even Access Daatbase in the internet has one big advantage: Also a website and also other clients than your application can connect to such databases easier than to DBFs.
Chriss