Error loading form что это

Error Explanation

The error that is been presented to you is telling you that a component on that form is not registered in the IDE, in this case TsStatusBar which is from the AlphaControls library: http://www.alphaskins.com/

The form would have been saved at some point with TsStatusBar placed on the form. When any component is added onto a form they leave references to the component in both the forms source file (*.pas) and the inside the forms dfm. This is why you are getting this error, because the component cannot be found, yet the references linking to it still remain.

Option 1 — Install the AlphaControls packge

The best option would be to install the components that are missing, this will solve your error problem as shown in your question.

Option 2 — Convert Project

AlphaControls provides a tool to convert a project from standard VCL to AlphaControls and vice versa, this may be an easier option then installing the AlphaControls package or manually editing source files, the convert tool is free. Just remember to make a backup before converting should anything go wrong.

Option 3 — Manually Editing the Source Files

You could manually remove these references yourself. Do note though, if you remove the references then Delphi will no longer know that the TsStatusBar was ever there, and without a doubt there will be code somewhere that would have interacted with this component which will create compiler errors.

As an alternative to removing the references, you could rename them from TsStatusBar to TStatusBar, which is a standard statusbar from the VCL. At worst there may be some small syntax errors that may need correcting. If you do decide to edit the forms source and dfm files then I would suggest you do it before loading the form into the IDE.

Option 4 — GExperts

You can also install an IDE Expert such as GExperts which can automate the process of renaming/converting component references.

I would however advise against removing or renaming the references in this circumstance as it seems the project is reliant on the AlphaControls package.

Summary

I can see there are more components from the AlphaControls package been used, so fixing the TsStatusBar error manually will only fix part of the problem.

If the project must remain in its current state then Installing the AlphaControls package is the way to go, if you are able to edit it then I would also suggest the project convert option, this way you won’t even need the AlphaControls package.

If you do chose to install the package, it is important to realise that once you install the package Delphi knows where the source files are to be able to compile. After installing the packages, goto Menu > Tools > Options from the IDE, then you need to go to Library and add the folder for the AlphaControls source to the library path. The source folder will be the one containing the most .pas files, but you could add all folders if you are unsure. If you don’t add to the Library path then Delphi will not be able compile when using the new components.

Recovering from corruption

This article may help if your database is already corrupt. To find out what causes corruption, see Preventing Corruption.

Before doing anything else, make a copy of the corrupted mdb file while Access is NOT running, and without overwriting any earlier backups. This lets you try different approaches and sequences if necessary.

Next, try the built-in repair utility. This very simple solution may work with corrupted indexes, and might even get rid of a corrupted object:

• In Access 2010, click Compact and Repair Database on the Database Tools ribbon.
• In Access 2007, click the Office button (top left), then Manage.
• In Access 95 — 2003, choose Database Utilities from the Tools menu.

If this does not work, follow the steps for the symptoms of your corruption below.

Symptom: Cannot open a form or report

While developing forms, reports, and the code in their modules, they are likely to corrupt. To work around this, import the other objects into a new database:

1. Create a new database.
2. Turn off the Name AutoCorrect check boxes:
   • In Access 2010: File | Options | Current Database.
   • In Access 2007: Office Button | Access Options | Current Database.
   • In Access 2000 — 2003: Tools | Options | General.

   For details of problems this mis-feature causes, see Failures caused by Name Auto-Correct.

3. Import the tables, or link them if the database is split.
   In Access 2007 or 2010, choose External Data | Import | Access.
   n Access 95 — 2003, choose Get External on the File menu.
4. Import the other objects (queries, forms, reports, macros, modules.)
5. Set minimal References under Tools | References (from the code window).
6. Compile (Debug menu, from the code window).

If one form or report is corrupt, the process will cease at step 5. You will see the name of the object that has not been imported, and you can then try the import again, skipping the bad form(s)/report(s). With a bit of luck, you may be able to import these from a previous backup.

Symptom: Number of records varies, depending how the data is sorted

This can happen if an index corrupts. To address this:

1. In the Relationships window, delete any relationships this table is involved in.
   In Access 2007 or 2010, click Database Tools on the ribbon, and choose Relationships.
   In Access 95 — 2003, choose Relationships from the Tools menu.
2. Open the table in design view. Open the Indexes box, and delete all indexes. Save. Close.
   In Access 2007 or 2010, Indexes is on the Table Tools ribbon.
   In Access 95 — 2003, it is on the View menu.
3. Select the table in the Database window (Access 95 — 2003) or Nav Pane (Access 2007 and later.) Copy and Paste, supplying a new name, and choosing Structure Only.
4. Create a query into the problem table. Check you see all records (sorting if necessary). Change it to an Append query, telling Access to append to the new table. Run the query. (Append is on the Query Tools ribbon in Access 2007 and 2010, or Query menu in Access 95 — 2003.)
5. Check that all the data is in the new table, and then delete the old table.
6. Compact the database to get rid of any reference to the problem table:
   • In Access 2010, Compact and Repair Database on the Database Tools ribbon.
   • In Access 2007, click Office Button (top left) | Manage | Compact.
   • In Access 95 — 2003, Tools | Database Utilities | Compact.
7. Rename the new table so it has the name of the old table.
8. Recreate the indexes and relationships you destroyed above.

In obstinate cases, you may need to recreate the tables programmatically. More information in knowledgebase article 815280.

Symptom: Some table rows show #Deleted

If this persists after restarting your computer, the table or its index is corrupt. Try the steps above for a corrupted index.

If that does not solve the problem:

1. Create a query into the table.
2. Attempt to exclude the corrupted rows. For example, if the corrupted row is between ID 25 and 27, try criteria of:
   = 27
3. Once you have the best range of uncorrupted records you can retrieve, change it to a Make Table query. Make Table is on Query menu in Access 95 — 2003; in Access 2007 or 2010, it is on the Query Tools ribbon under Query Type.
4. Run the query to create the new table.
5. Delete the old table.
6. Compact the database to get rid of any reference to the problem table:
   • In Access 2010, Compact and Repair Database on the Database Tools ribbon.
   • In Access 2007, click Office Button (top left) | Manage | Compact.
   • In Access 95 — 2003, Tools | Database Utilities | Compact.
7. Rename the new table to the name of the old one.
8. Recreate the indexes and relationships you destroyed above. If you are unable to create a relationship, use the Unmatched Query Wizard to identify which records are missing.

Again, programmatic re-creation may help.

Symptom: Memo field contains strange characters.

Access uses a pointer to another location for the data in large fields (memo, hyperlink, or OLE Object). If the pointer is written incorrectly, the field displays garbage.

To address this kind of corruption, delete the memo field from your table. Compact to get completely rid of it:

• In Access 2010, Compact and Repair Database on the Database Tools ribbon.
• In Access 2007, click Office Button (top left) | Manage | Compact.
• In Access 95 — 2003, Tools | Database Utilities | Compact.

Then create the memo field again. If the data is important, you may be able to link to an older backup (File | Get External | Link in Access 95 — 2003; External Data | Import in Access 2007 and 2010), create a query joining the current and older copy on the primary key, and then change it to an Update query to update the now blank memo field with the contents of the old one.

If the strange characters appear only in the query, not when you view the table, this is not a corruption. This occurs when JET is unable to determine the data type of the query field, and is triggered by lots of situations. Solutions for this non-corruption issue include:

• Add a primary key to your table.
• Explicitly typecast the field.
• Do not concatenate text fields that generate more than 255 characters.

Symptom: «An error occurred while loading Form_FormName»

If you receive this error when trying to convert from one version of Access to another, your database is partially corrupt. Decompile a copy of your database.

1. Make a copy of the mdb file while Access is not running.
2. Compact:
   • In Access 2010, Compact and Repair Database on the Database Tools ribbon.
   • In Access 2007, click Office Button (top left) | Manage | Compact.
   • In Access 95 — 2003, Tools | Database Utilities | Compact.
3. Close Access. Open a command prompt, and enter something like this. It is one line, and include the quotes:
   «c:Program FilesMicrosoft officeofficemsaccess.exe» /decompile «c:My DocumentsMyDatabase.mdb»
4. Compact again.
5. Try the conversion again.

Symptom: «Error Accessing File. Network Connect May Have Been Lost»

This is a nasty bug in the early releases of Access 2000, and there is no easy fix. The corruption will not occur if you apply the service packs, or use later versions of Access.

Knowledgebase article 304548 explains that the problem was with version 6.3.91.8 of Vbe6.dll. If you import code from another version (typically Access 97) and close the database without recompiling, your code is hosed.

Symptom: «AOIndex is not an index in this table»

Dirk Goldgar (Microsoft Access MVP) traced this problem back to faulty entries in the MSysAccessObjects table. He reports that the problem can be solved by deleting the faulty entries, and creating a valid primary key.

Download his solution from http://www.datagnostics.com/dtips/fixaoindex.html, or use the use the code (at right) like this:

1. Make a copy of the mdb file while Access is not running.
2. In another database, paste the function at right into a module.
3. Open the Immediate Window (Ctrl+G), and enter:
   FixBadAOIndex(«C:MyPathMyFile.mdb»)
   using your database name in the quotes.

Symptom: » Isn’t an Index in This Table»

This corruption of the MSysObjects table occurs in Jet 3.x (Acc 95 or 97). Microsoft released a utility (jetcomp.exe) to address this issue. For more information, see the knowledgebase article for Access 97 or Access 95.

Symptom: Key field is no longer primary key, and relationships are gone

When you compact/repair a database, Access rebuilds the indexes. If it discovers data the violates the index (such as duplicate values in a unique index or primary key), it drops the index. Your table still has all the data, but the index is gone. If you have relationships to other tables that depend on this index to maintain referential integrity, the repair process has to drop those relationships as well.

When this happens, it creates a new table to notify you of the problem. You will find a table with a name such as Compact Errors. The creation date lets you know when Access dropped the index/relations.

To fix this situation, you need to identify the records that violate the index. To find the problem records, use the Find Duplicates Query Wizard (first dialog when you create a new query.) You can then delete the bad records, and mark the field as primary key again.

If a relation was dropped, use the Find Unmatched Query Wizard to identify the bad records in the related query. Delete them or reassign them to the correct key value. You can then create the relation again (Tools menu.)

SaveAsText / LoadFromText

This is an undocumented technique that may rescue a bad form or report by exporting it to a text file, and instructing Access to recreate it from the text file.

1. Make a backup of your database.
2. Open the code window (Ctrl+G) and look through the modules (Windows menu.)
   If you can see a module for this form/report, copy the text out to Notepad, and save it.
3. Open the Immediate Window (Ctrl+G), and export the form/report as a text file. Enter something like this:
   SaveAsText acForm, «Form1», «C:MyFolderForm1.txt»
   substituting your form name for Form1 and your directory for MyFolder. Use acReport if the problem object is a report.
4. Verify that the text file was created in the folder you specified.
5. Delete the form from the database.
   Select it in the Navigation Pane (Access 2007 or later) or Database Window (previous versions), and press Del.
6. Compact the database:
   • In Access 2010, Compact and Repair Database on the Database Tools ribbon.
   • In Access 2007, click Office Button (top left) | Manage | Compact.
   • In Access 95 — 2003, Tools | Database Utilities | Compact.
7. Open the Immediate Window (Ctrl+G). Enter something like this:
   LoadFromText acForm, «Form1», «C:MyFolderForm1.txt»
   substituting the same things you did at Step 3 above.

You will receive an error message at Step 3 if Access cannot make sense of the form to export it. You will have to delete the form and re-create it, but if you saved the code at Step 2 you can at least paste that back into the new form’s module after you create it.

If Step 3 works without error, there is a good chance the rest of the steps will succeed too.

Other Resources

If none of these steps solve your problem and you need professional help, talk to a professional recovery service such as EverythingAccess. Their repair guide is also a good resource.

Источник

Contact US

Thanks. We have received your request and will respond promptly.

Come Join Us!

• Talk With Other Members
• Be Notified Of Responses
  To Your Posts
• Keyword Search
• One-Click Access To Your
  Favorite Forums
• Automated Signatures
  On Your Posts
• Best Of All, It’s Free!

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Error Loading form

Error Loading form

Error Loading form

I have a form that has been acting weird at a clients site. They are running just an executable but for some reason they get an error opening a form from time to time. If I remove a view from the data environment and rebuild the exe and they then open the form from this exe the form opens. I then add the view back in, rebuild and this exe works for the client again. It happens every couple weeks and I don’t know why it happens. Any ideas?

RE: Error Loading form

What is the exact text of the error message? It should have some information on exactly WHY it can’t load the Data Environment and which «record» it crashed on. The record indicated is in the form’s structure table. (The *.scx file)

Of course, since you pinpointed the View as being the problem, obviously the record it’s crashing on is the one for the View.

In any case, the error message might give us more insight into what could be causing the error.

RE: Error Loading form

RE: Error Loading form

That’s a tough one. Let’s just make sure here.

Let’s assume that your form’s name is «Myform». If not, substitute the real name. Run the following and tell me what it comes up with:

USE MyForm.SCX
GOTO 7
?Properties
USE

Ian

RE: Error Loading form

Sorry it took so long to reply, I hope you can still help me out

I did that and this is what I got:

Left = 150
Top = 140
Width = 95
Height = 90

Alias = «wkloaddetail»
CursorSource = ..wkloaddetail.dbf
Name = «Cursor5»

I added this working table to the data environment because the view uses it but I still get the same problem.

RE: Error Loading form

RE: Error Loading form

Ok. That tells you the table that is causing the problems. Now, from the Command Window, see if you can open the table.

CD (insert table directory here)
USE wkloaddetail

See if you get any errors there.

It’s possible that this table is corrupted at the client site. Is it possible to try this there? You might need to replace the table.

Do you have any problems at all in your development environment?

RE: Error Loading form

In the form load I have this code that creates the table:

select loaddetail.* from loaddetail into table wkLoadDetail

index on wkLoadDetail.loadnum + wkLoadDetail.salesnum tag loadsales
=cursorsetprop(‘buffering’,5,’wkloaddetail’)

I don’t delete it. I just remove the view from the form not the project.

RE: Error Loading form

That might be your problem. The Data Environment is loaded already before your form LOAD event takes place. Try moving this code to the BeforeOpenTables event of your Data Environment.

RE: Error Loading form

I’ll try that and I’ll get back to you if that is the solution. Have to wait and see if the error comes back up at the clients site.

RE: Error Loading form

That seems to have worked for the Foxpro application with the Foxpro database that I was running, but it has been upgraded to an SQL Server database and I can’t have the code in the BeforeOpenTables event of your Data Environment.

The loaddetail is now a remote view. The same error is occuring again.

select loaddetail.* from loaddetail into table wkLoadDetail
index on alltrim(str(wkLoadDetail.loadnum)) + wkLoadDetail.salesnum tag loadsales

Still have that in the load and edit buttons of the form

RE: Error Loading form

If you look at tools -> options -> file locations, you will see that there are paths where foxpro is looking when it searches for a file or table or etc.

It puts these directories automatically in it. Why. Do not know. When we cleared it, we get the same sort of error with a table and view we added recently to our database.

But when the directories are filled everything works fine. I wonder of these directories are build in the .EXE. Changing any value then can give problems at the client side.

We used set path in our code to avoid problems with finding any table or view.

RE: Error Loading form

I have put the set path code into my form now and I’ll wait and see if the error occurs still at the client side.

RE: Error Loading form

RE: Error Loading form

RE: Error Loading form

No go, I can’t get the form to open up with either wkloaddetail or lv_wkloaddetail in the data environment.

RE: Error Loading form

I konw a way that must work but it is not a beautiful solution. Before you try to open say once:

Use MyTable or use the view.

After that open the for. I am sure itt will work but we still don’t know what the problem is unfortunately. Try it.

RE: Error Loading form

In all honesty, you shouldn’t even HAVE that table in the data environment since it doesn’t actually exist until your SELECT statement executes. In fact, it shouldn’t hurt anything at all for it to be taken out. Just remember to close the table in the form’s UNLOAD event:

IF USED («wkloaddetail»)
USE IN wkloaddetail
ENDIF

Ian

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Источник

Hi there!

I have been trying to get the SharePoint integration to work on the portal.

I created an Entity Form that should display a tab of the Account Web Form containing the Document Location on the Portal. However, I have been having some trouble with this. After an error message showed up (The record you are looking for couldn’t be found.) I tried testing with other entities and forms, to see if it was the entity/form itself or something else, however the error still showed up.

After a while I decided to reconfigured everything from scratch, reset the Portal and enabled SharePoint integration again.

Now I am having this error on the Portal Editor :

I checked the Entity Permissions and that the Entity Permissions is enabled and all seems to be fine. The Form Mode is set to Edit, Record Source Type is Query String and Record ID Query String Parameter Name is id. What I did notice however, is that when I go on the Portal on the Web Page where there is the Entity form, the URL does not display «id=000…etc» but it just displays the URL/partial URL.

Does anyone have any suggestions please?

Join Tek-Tips^® Today!

Join your peers on the Internet’s largest technical computer professional community.
It’s easy to join and it’s free.

Here’s Why Members Love Tek-Tips Forums:

• Talk To Other Members
• Notification Of Responses To Questions
• Favorite Forums One Click Access
• Keyword Search Of All Posts, And More…

Register now while it’s still free!

Already a member? Close this window and log in.

Join Us             Close

Ошибка Объяснение

Представленная вам ошибка говорит о том, что компонент в этой форме не зарегистрирован в среде IDE, в данном случае TsStatusBar из библиотеки AlphaControls: http://www.alphaskins.com/

Форма была бы сохранена в какой-то момент с TsStatusBar, помещенным в форму. Когда какой-либо компонент добавляется в форму, они оставляют ссылки на компонент как в исходном файле формы (*.pas), так и внутри формы dfm. Вот почему вы получаете эту ошибку, потому что компонент не может быть найден, но ссылки на него все еще остаются.

Вариант 1. Установите пакет AlphaControls.

Лучшим вариантом будет установка отсутствующих компонентов, это решит вашу проблему с ошибкой, как показано в вашем вопросе.

Вариант 2 — преобразовать проект

AlphaControls предоставляет инструмент для преобразования проекта из стандартного VCL в AlphaControls и наоборот, это может быть более простой вариант, чем установка пакета AlphaControls или ручное редактирование исходных файлов, инструмент преобразования является бесплатным. Просто не забудьте сделать резервную копию перед преобразованием, если что-то пойдет не так.

Вариант 3 — Редактирование исходных файлов вручную

Вы можете вручную удалить эти ссылки самостоятельно. Однако обратите внимание, что если вы удалите ссылки, Delphi больше не будет знать, что TsStatusBar когда-либо был там, и, без сомнения, где-то будет код, который взаимодействовал бы с этим компонентом, что приведет к ошибкам компиляции.

В качестве альтернативы удалению ссылок вы можете переименовать их из TsStatusBar в TStatusBar, которая является стандартной строкой состояния из VCL. В худшем случае могут быть небольшие синтаксические ошибки, которые необходимо исправить. Если вы решите отредактировать исходный код форм и файлы dfm, я бы посоветовал вам сделать это перед загрузкой формы в IDE.

Вариант 4 — GExperts

Вы также можете установить эксперт IDE, такой как GExperts, который может автоматизировать процесс переименования/преобразования ссылок на компоненты.

Однако я бы посоветовал не удалять или переименовывать ссылки в этом случае, поскольку кажется, что проект зависит от пакета AlphaControls.

Заключение

Я вижу, что используется больше компонентов из пакета AlphaControls, поэтому исправление ошибки TsStatusBar вручную решит только часть проблемы.

Если проект должен оставаться в своем текущем состоянии, то установка пакета AlphaControls — это путь, если вы можете его редактировать, я бы также предложил вариант преобразования проекта, таким образом, вам даже не понадобится пакет AlphaControls.

Если вы решили установить пакет, важно понимать, что после установки пакета Delphi знает, где находятся исходные файлы, которые можно скомпилировать. После установки пакетов перейдите в «Меню» > «Инструменты» > «Параметры» из IDE, затем вам нужно перейти в «Библиотека» и добавить папку для исходного кода AlphaControls в путь к библиотеке. Исходная папка будет содержать наибольшее количество файлов .pas, но вы можете добавить все папки, если не уверены. Если вы не добавите путь к библиотеке, Delphi не сможет скомпилироваться при использовании новых компонентов.