I have an application originally written in FM5. I don't have any manuals for FM5 and I can't find this documented in FM7 ... can anyone tell me what is the meaning of a number following the filename in the Open File statement?

I have an application originally written in FM5. I don't have any manuals for FM5 and I can't find this documented in FM7 ... can anyone tell me what is the meaning of a number following the filename in the Open File statement?

I have an application originally written in FM5. I don't have any manuals for FM5 and I can't find this documented in FM7 ... can anyone tell me what is the meaning of a number following the filename in the Open File statement?

It's usually the IP number of the host machine, if the file is hosted in FM Server.

Otherwise (and I suspect more likely) it's part of the file name, where the file has been copied and renamed "2" to distinguish it from other copies.

It's usually the IP number of the host machine, if the file is hosted in FM Server.

Otherwise (and I suspect more likely) it's part of the file name, where the file has been copied and renamed "2" to distinguish it from other copies.

It's usually the IP number of the host machine, if the file is hosted in FM Server.

Otherwise (and I suspect more likely) it's part of the file name, where the file has been copied and renamed "2" to distinguish it from other copies.

This system does not use FM Server. It is a peer-to-peer system.

In my experience, any time the scripts have referred to a non-existing file I get an error message and I haven't got any error messages for these files ... so I wondered if it had anything to do with self-joins?

I have been asked to help upgrade this system but there is no documentation so I am trying to figure out what on earth it is doing.

This system does not use FM Server. It is a peer-to-peer system.

In my experience, any time the scripts have referred to a non-existing file I get an error message and I haven't got any error messages for these files ... so I wondered if it had anything to do with self-joins?

I have been asked to help upgrade this system but there is no documentation so I am trying to figure out what on earth it is doing.

This system does not use FM Server. It is a peer-to-peer system.

In my experience, any time the scripts have referred to a non-existing file I get an error message and I haven't got any error messages for these files ... so I wondered if it had anything to do with self-joins?

I have been asked to help upgrade this system but there is no documentation so I am trying to figure out what on earth it is doing.

You mean the files are being hosted with FMP, or the files live on a shared network volume?

Sharing FMP files on a network volume is bad. No other word for it. The files will have some level of corruption, guaranteed.

You mean the files are being hosted with FMP, or the files live on a shared network volume?

Sharing FMP files on a network volume is bad. No other word for it. The files will have some level of corruption, guaranteed.

You mean the files are being hosted with FMP, or the files live on a shared network volume?

Sharing FMP files on a network volume is bad. No other word for it. The files will have some level of corruption, guaranteed.

Interesting question ... maybe there is a terminology problem. I assume (and you know what that stands for) that they are using the principle that the first user hosts the database. Is there another way to do it?

Interesting question ... maybe there is a terminology problem. I assume (and you know what that stands for) that they are using the principle that the first user hosts the database. Is there another way to do it?

Interesting question ... maybe there is a terminology problem. I assume (and you know what that stands for) that they are using the principle that the first user hosts the database. Is there another way to do it?

I discovered the answer to my question: the parameter in the Open Files statement is a File Reference. That was not clearly documented. In fact the Help file for Open File is quite unclear (referencing Specify when it is not in the syntax.)

However, now that I have looked at the File References, I see that they are in Windows format (the platform on which it runs) ... so that raises the question of what happens when the application is executed in a Mac environment? Would this explain why it takes so long to open files?

I discovered the answer to my question: the parameter in the Open Files statement is a File Reference. That was not clearly documented. In fact the Help file for Open File is quite unclear (referencing Specify when it is not in the syntax.)

However, now that I have looked at the File References, I see that they are in Windows format (the platform on which it runs) ... so that raises the question of what happens when the application is executed in a Mac environment? Would this explain why it takes so long to open files?

I discovered the answer to my question: the parameter in the Open Files statement is a File Reference. That was not clearly documented. In fact the Help file for Open File is quite unclear (referencing Specify when it is not in the syntax.)

However, now that I have looked at the File References, I see that they are in Windows format (the platform on which it runs) ... so that raises the question of what happens when the application is executed in a Mac environment? Would this explain why it takes so long to open files?