Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How can I make Paradox open a form over the network?

Status
Not open for further replies.

timoteo

Technical User
Sep 17, 2002
72
US
I have installed Paradox on one of our clients and I can open tables and queries, but when I try to open a form I receive the following error message:

"Error 4324: One or more of the tCursors failed to open."

What do I can I do to run a form over the network?

Thank you in advance for any help.

Timoteo
 
This is most likely an alias issue. First, did you use aliases? If so, did you make certain to point them to your tables on the network? An easy way to resolve this is to open up paradox and go to Tools->Alias Manager. Look at the public alias names and paths. Your error message may include the alias and table name the tCursor was referencing. If so, examine the alias list and see if that alias points to where that table is now located. It may also be that a project alias is being set in the code. In that case it will require debugging to find and correct the problem.

Mac :)

"Gurth a choth-en-America! Tôl acharn..."


langley_mckelvy@cd4.co.harris.tx.us
 
timoteo,

Also, if you're working with source versions of the forms (FSL files, as opposed to delivered .FDL versions of the forms), you may be able to locate the exact line of code causing the problem (assuming it is based on code).

To do this, open your FSL in a Design windows and then see if you have a Program menu on the main menu. If not, then choose Tools | Settings | Developer Preferences, place a checkmark in the Show developer menus combobox on the General tab, and then choose OK.

Next, choose Program | Compiler Warnings and then choose Compile with Debug. Save your form and then run it.

You will still receive the error message, but it should now contain additional information you can use to troubleshoot the problem, such as the name of the method containing the code that didn't work and the line the error occured on.

Hope this helps...

-- Lance
 
Langley, Footpad,

You both hit the problem right on, I had to add an alias to the client machine because the project alias was set in the code.

Thank you for your help.

Timoteo
 
That's why Lance and I get the big bucks for doing this ;-) Mac :)

"Gurth a choth-en-America! Tôl acharn..."


langley_mckelvy@cd4.co.harris.tx.us
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top