Bug with components remembering old db paths, when migrated to a production server ?

[kthibeault1965]

I am working with other developers who are publishing to a common web server

Whenever they work locally, then zip the db, and expand to the common webserver to deploy it, the grid components DONT WORK, and retain the old dbf path. The fix is to go into each component, while working on the server itself and RESAVE each one. One by one. We have investigated all alias settings there are,, and totally stumped.

Any help out there?

the grid starts to display in on the page.. then when the first record is shown, no data comes.. on the following error message

Error 5 - Error loading c:\users\�����\desktop\������ �����\webcontactlist\checklist.dbf: The system cannot find the path specified. c:\users\�����\desktop\������ �����\webcontactlist\checklist.dbf

Yes the characters are a bit strange, I am working with Russian developers. I am quite sure this is not an issue.

MY bigger concern, is the portability of the Alpha development solution. You should be able to develop a page and an component on a separate machine, and include that on the production server at a later date, WITHOUT the component "remembering" an old and bad database path.

Or am i nuts.

[APFCClyde]

Re: Bug with components remembering old db paths, when migrated to a production serve

From the release notes, this might help:

Web Applications - Filenames - Resolving Aliases - When you build a web application that uses filenames for Alpha Five Objects (i.e. .dbf files, .ddd and .set dictionary files, etc.), the typical convention is to use an alias for the file path in the filename. For example, the Xbasic in a typical .a5w page, or event handler in a component might look like this:

t = table.open("[PathAlias.ADB_Path]\customer.dbf")

Currently, this alias is replaced at publish time, using the definition for the alias that is stored in the publishing Profile. So, assume that you have defined a profile called 'Server1', and you defined the folder for [PathAlias.ADB_Path] to be "c:\datafolder", then at publish time, all references to this alias will be replaced by "c:\datafolder".

Now, you can choose not to resolve aliases at publish time, but instead resolve them at run-time, based on the information in the a5_application.a5i file. The a5_application.a5i file gets published automatically every time you publish any files. The a5_application.a5i file contains a section in it that defines the physical path for each alias. For example, a typical entry in the a5_application.a5i might look like this:

Dim _aliases_ as c
_aliases_ = <<%txt%
[PathAlias.ADB_Path]|C:\DataFolder
[PathAlias.Northwind]|C:\MDBFiles
%txt%

The huge advantage of resolving aliases at run-time (rather than publish time), is that by simply making a single change in the a5_application.a5i file, you can point your entire application at a different set of files and reports.

Starting with this version, path aliases are now not resolved at publish time. To take advantage of this change, you must re-publish your application. If you want to continue resolving path aliases at publish time, you can still do so by going to View, Settings, Preferences, Web Publishing, Alias Resolution and selecting the 'Publish Time' option.

Since you are not publishing but simply copying the files onto the webserver, this technique should work for you.

[kthibeault1965]

Re: Bug with components remembering old db paths, when migrated to a production serve

thanks for this - NO LUCK however.

I Installed patch, republished with publish time selected..and still can not see dbf in grid.. with same error message.

any other ideas?

thanks

[APFCClyde]

Re: Bug with components remembering old db paths, when migrated to a production serve

Pull up the component in dev, click on the Xbasic tab & make sure you have a line that looks like this:

tmpl.DBF.table_name = "[PathAlias.ADB_Path]\checklist.dbf"

Sounds like it might be hardcoded to the invalid path you're seeing in the error, in which the case the path resolution won't work.

[kthibeault1965]

Re: Bug with components remembering old db paths, when migrated to a production serve

this is what is in there:
DIM tmpl.DBF.Tables[tmpl.DBF.table_count] as P
tmpl.DBF.tables[1].physical_name = "[PathAlias.ADB_Path]\checklist.dbf"

I am also having trouble with other grids as well, not just this one.

but the fix USUALLY involves resaving it. With one particular one, even that wont work.

very frustrating
thanks for your thoughts anyway Clyde

[APFCClyde]

Re: Bug with components remembering old db paths, when migrated to a production serve

What version of A5 are you using?

[NoeticCC]

Re: Bug with components remembering old db paths, when migrated to a production serve

I had this problem in the previous build I believe...