Package naming cause problem in runtime

0 views
Skip to first unread message

Chau Chee Yang

unread,
Oct 30, 2007, 10:34:44 PM10/30/07
to
Hi,

I use dynamic packages in my application development.

I have the following scenario:

File "db.package1.dpk"
----------------------
output: SQL.db.package1.bpl
dcp: db.package1.dcp

File "db.package2.dpk"
----------------------
require: db.package1.dcp
output: SQL.db.package2.bpl
dcp: db.package2.dcp

File "myapp.dpr"
----------------
output: myapp.exe (built with runtime packages rtl and vcl)

myapp.exe will load "SQL.db.package2.bpl" at runtime thru
SysUtils.LoadPackage routine. However, this will cause the following
runtime errors:

1. "This application has failed to start because SQL.db.bpl was not
found. Re-installing the application may fix this problem".

2. Project myapp.exe raised exception class EPackageError with message
'Can't load package c:\output\SQL.db.package2.bpl. The specified module
could not be found.'

If I name my package file as "db_package1.dpk" and "db_package2.dpk"
respectively, then the runtime packages were loaded without error. I
suspect the problem was related to how the package file name. I use dot
(".") to name the packages.

Any ideas? Please advice. Thank you.

--
Best regards,
Chau Chee Yang

E Stream Software Sdn Bhd
URL: www.sql.com.my
SQL Financial Accounting

Reply all
Reply to author
Forward
0 new messages