I am not an Alpha 5 developer, and am posting this on behalf of a colleague...
Are there guidelines as to 'best practices' in making code portable between different deployment scenarios?
My colleague has hust hit a problem in a network environment whereby client PCs receive error messages when system cards are run - the problem would appear to be where the card explicitly states the full path to the bdf file. In this particular case the data resides on the server in C:\appName\. C:\appName\ has then been set up as a share as S: on the client pc's. It would then appear that when the system card runs and tries to use the explicit C:\appName\...dbf table, the table cannot be found as C:\appName does not exist on the client.
Also my colleage has also 'split' the data and created a subdirectory under appName called 'accounts' where he has put all the accounts related tables. The problem appears to be here, that on the 'system cards', you can either specify the explicit full path of a table OR the tableName.dbf. How then, in this case where accounts/tableName.dbf needs to be specified, can I do that? What a relative path list that is specified in the card, the Save throws an error. So, in this case it seems the only option is to enter a full path - but that then causes the issue above re portability.
Obviously something is being missed this end that's causing the confusion.
Sorry if the explanation is a bit garbled - I'm not too sure of the Alpha 5 terminology etc.
Are there guidelines as to 'best practices' in making code portable between different deployment scenarios?
My colleague has hust hit a problem in a network environment whereby client PCs receive error messages when system cards are run - the problem would appear to be where the card explicitly states the full path to the bdf file. In this particular case the data resides on the server in C:\appName\. C:\appName\ has then been set up as a share as S: on the client pc's. It would then appear that when the system card runs and tries to use the explicit C:\appName\...dbf table, the table cannot be found as C:\appName does not exist on the client.
Also my colleage has also 'split' the data and created a subdirectory under appName called 'accounts' where he has put all the accounts related tables. The problem appears to be here, that on the 'system cards', you can either specify the explicit full path of a table OR the tableName.dbf. How then, in this case where accounts/tableName.dbf needs to be specified, can I do that? What a relative path list that is specified in the card, the Save throws an error. So, in this case it seems the only option is to enter a full path - but that then causes the issue above re portability.
Obviously something is being missed this end that's causing the confusion.
Sorry if the explanation is a bit garbled - I'm not too sure of the Alpha 5 terminology etc.
Comment